I'm but a lowly humble indie developer unschooled in techniques such as test driven development, yet I often find myself doing something like what the author de

I'm but a lowly humble indie developer unschooled in techniques such as test driven development, yet I often find myself doing something like what the author describes. The bit that rings true for me is that he decided to "write out a script using the yet unwritten API". I have found my designs to be much more succinct & workable when instead of writing a bunch of classes then figuring out how to get them all to play together, write the code where the proverbial tyres hit the road & then go back to fill in the details. I'm sure the more experienced software engineers out there would facePalm at this method & it's obviousness, but it gets the job done ;)