Why A Name Matters My team just changed our name from the Platform Team to the Engineering Team. We did this after our new editor-in-chief asked us to reflect on what we wanted to be called, and on how our tech team was different from the other tech team, and on what it was that
“What makes a Muppet, a Muppet?” wondered our designer. He’d made a prototype illustration, but wasn’t happy with it — he didn’t feel it was immediately recognizable as a Muppet. He’d come to the tech area for input, and we were happy to oblige. We analyzed the hell out of the visual ontology of Muppetdom.
This weekend I’ll be at NICAR, the conference that last year inspired me to ponder what humanists could learn from journalism. That means I don’t have a lot of time to write. But I wanted to share an screenshot from the NICAR schedule that I think is worth a thousand words: This is what a
Dr. Karen Kelsky (aka The Professor Is In) asked if I had any step-by-step posts on how I got my current job. That’s its own story, which I will tell at some point, but this is a quick overview of how I got where I am, with links to all the practical posts I could
Last week, I talked about the difficulty of finding a cool code project to care about if you didn’t already know how to code. Because of that, I’m trying to think of things that inspired me even before I knew how to write the code for them. Maybe I’m not an adequate code evangelist. I cannot