Documentation Driven Design

In my latest project The Podcast Database I’m going to try tackling the planning stage in a different way than I usually do

Normally when I’m trying to start a personal project I’ll whip out a notepad and pen and start scribbling.. well, usually I at least jot down the date and the title of the project. After that I tend to give up on that and dive right into the code.

On this one I’m going to try something different, I’ve started documenting The Podcast Database before any code has been written. That way I know what I’m aiming for and as a bonus don’t have to document anything when I’m done. Woohoo!



Sign up for emails about the things

Sign up to my (at most) weekly mail list. I'll send general updates to the list, new projects and whatnot. Not every single post as it comes out, but a summary mixed in with random cool tech I find around the net. For more info checkout the subscribe page

I'll never sell, give, transfer, trade your contact details with any other person, company, or other entity and you're free to click that big unsubscribe link at the bottom of each message whenever!