I did take a few pictures of the final boards though: Photo of a few final Scrabble boards Days 1 and 2 | “sketching” I wish I had the foresight to track which words were played and did so for the first two games of 2014 but lost motivation because I was prolonging each game by pausing after each turn to record which word was played, where it was played, and how many points it was worth. Screenshot of Scrabble database Screenshot of original dashboard After each game, I diligently entered the score data into my own MySQL database to query and generate a bare bones dashboard.

I decided to track the weekly games with my father-hoping to chart our scores and find interesting patterns in our playing styles. (My father was an English teacher and I was always the scorekeeper.) They never let me win and for that I’m thankful but during the early years, they were formidable opponents-and still are!įast forward to 2013. My grandmother has is a force to be reckoned with in the game, my father has played for ages, and both of them taught me when I was about 12 as a way to build my language and math skills. The game has been part of my family since before I was. Taking a step back, it’s important to mention that I play a lot of Scrabble. Back in 2013, when I just started getting seriously interested in the artistic side of data visualization, I did what any newly-obsessed data junky would do: I picked a familiar subject and tracked it obsessively. Maybe I knew one day I would do more with it. Unlike many of my projects, I didn’t need to start by collecting data because I had already done so.three years ago. Whether or not that happened will be left to the reader but below is the story of how it came to be. When Shirley and Nadieh asked me to make a guest post for Data Sketches, I jumped at the opportunity but immediately panicked a little because I had agreed to the daunting task of creating something like their wonderful projects over the past six months. This post was been reproduced here with their permission on Decemand backdated with the date of the original release. Special thanks to Alexander Bohn, Anselm Levskaya, and Adam Suharja for beta testing and essential feedback.Note: This was a guest post on Data Sketches-a collaboration between by Nadieh Bremer and Shirly Wu wherein they created 24 data visualization projects on a wide variety of topics that interested them.

PlotDevice is primarily the work of Christian Swinehart, with significant API-design contributions from Marcos Ojeda. Despite these changes, it maintains backward compatibility with all the original NodeBox commands. Is the use of the Python with statement to Of Python and macOS and adding syntactic sugar as judiciously as possible. PlotDevice is an “existential refactor” of the NodeBox code, updating it to work with modern versions Twofold: offering a powerful graphics tool for Pythonistas and providing a learning environment for budding programmers. This project is a fork of the NodeBox 1 application which was developed in theĮarly oughts at the Experimental Media Research Group in Antwerp and derived from an early version of DrawBot.

Nodebox import lines