software development practices
Today's rumination is not for the weak of heart. It's from the venerable C2 Wiki page Code For The Maintainer: Always code as if the person who ends up maintaining your code is a violent psychopath who knows where you live. Perhaps a little over the
programming languages
Steve Yegge’s latest, Code’s Worst Enemy, is like all of his posts: rich, rewarding, and ridiculously freaking long. Steve doesn’t write often, but when he does, it’s a doozy. As I mentioned a year ago, I’ve started a cottage industry mining Steve’s insanely great
software development concepts
In a previous entry, I touched on the broken window theory. You might be familiar with the Pragmatic Progammers’ take on this: Don’t leave “broken windows” (bad designs, wrong decisions, or poor code) unrepaired. Fix each one as soon as it is discovered. If there is insufficient time to
code organization
I generally dislike these kinds of “Me, too!” posts, but I have to make an exception for Ned Batchelder’s excellent blog entry on deleting code. I’ve often run into this phenomenon with other developers, and it bugged the heck out of me, although I couldn’t quantify exactly