Earlier this year I was listening to an episode of DotNetRocks on which Don Box and Chris Sells discussed the future of technical book publishing. Don was asked something about what blogs/books he reads, and his response — very roughly paraphrased — was that he’s so busy producing stuff that he doesn’t have a whole lot of time to be consuming stuff. If we use the analogy of the trade surplus/deficit, Don has an enormous public information surplus with the world.
I, on the other hand, have had a huge public information deficit over the past couple of years — consuming orders of magnitude more than I have published to the world. That’s not to say I’ve just been sitting around doing nothing, only that all my production has been private to me, my employers, and my clients. While this blog has sat idle, I find myself producing emails and documents suggesting how my teams can do things better and guiding those teams toward tools and practices that can help us make better software with fewer resources.
I don’t claim that any of those ideas are original (maybe a few), but I do think that the experience of applying those ideas in real projects over the past dozen years is worth something. Writing about those experiences is really just for myself and for my own reasons, but if some nugget of info helps someone somewhere be a better developer in some small way — well, that would help me balance my information deficit and it would be really cool, too.
So here’s goes…