30 Day Challenge: Release or Die Trying
When I first stumbled on a few blog posting ceremoniously declaring the author's Challenge, I shrugged and kept browsing for something more interesting. It just seemed to gimmicky and faddish.
While the idea of a 30 day challenge isn't new, the idea of applying it to software development certainly is. Forget the waterfall, or agile methodologies -- you have exactly thirty (30) days to design, craft, code, debug and release a usable software product that your target audience will pay for. And for good measure add the prospect of bragging rights (or public humiliation) if you succeed (or fail).
Well today, as I look at stacks of time sheets and invoices from consulting, I notice that my product still hasn't shipped.
I'm in. 30 days to release version 1.0.
Labels: ThirtyDayChallenge
