Skip to main content

Geek, coder, gamer, tinkerer, husband, father, system admin, web developer, and American cyborg, though not necessarily in that order. Creator of Mythic Wars (card game).


The Programmer's Credo: we do these things not because they are easy, but because we *thought* they were going to be easy.
HT /


👍 Programming Sucks

"This is what it is to learn programming. You get to know your useful tools, then you look around, and there are some handy new tools nearby and those tools show you the bottomless horror that was always right next to your bed."

FWIW, I don't think it sucks quite this much, but it is kinda scary how much of this rings true.



Ahh, StackOverflow: come for the programming questions, stay for the DnD clarifications (and the Harry Potter miscellanea).


Fatigue and Mastery

1 min read

Tero Parviainen (@teropa) has a nice piece about [Overcoming Javascript Framework Fatigue](, but don't let the title fool you - much of the advice can be applied those who work (and live) in most any rapidly-evolving field. Plus, it contains [one of the best quotes]( from Rich Hickey (@richhickey, the creator of [Clojure]( about what skills a developer really needs to have (and those skills have nothing to do with preferred language or framework):

> Programming mastery has little to do with languages, paradigms, platforms, building blocks, open source, conferences etc. These things change all the time and are not fundamental. Knowledge acquisition skills allow you to grok them as needed. I'd take a developer (or even non-developer!) with deep knowledge acquisition and problem solving skills over a programmer with a smorgasbord of shallow experiences any day.

Via [HTML5 Weekly](