From the article: I deliberately decided to experiment with test-first development a few months ago. and the programs I am writing are my own personal projec

From the article: I deliberately decided to experiment with test-first development a few months ago. and the programs I am writing are my own personal projects If you have no real experience with TDD and you're hacking away at personal projects, I can see where you might not find TDD to be useful. If you're experienced with it and working on a project that is going to be sizable and for use by others who might be paying to use it, TDD is indispensable. I've seen a lot of fads come and go over the years. I've tried many of them out just to see how they fit my style of working. TDD is one of those paradigms that has withstood the test of time. Much more important than code coverage and ability to make changes without breaking things as mentioned in the article, TDD forces you to think about your software components from the client perspective first. It's that discipline that I appreciate more than anything.