[
bob
]
22:45, Sunday, 15 June 2003
On a recent project, I've decided to take a lateral step from test-driven development towards documentation-driven test-driven development, or d2td2.
Basically, I write the docs so I have the requirements, which allows me to write the tests, which then help write the code itself. Things that make sense while writing the tests or code start looking goofy sometimes when you have to describe them in prose documentation. So, if you feel like an ass trying to describe how to use a component, that's a code smell that means you probably need to refactor.
So, I'd like to solicit experiences from others if you've used this type of development before. Most everywhere I've worked, either commercially or on open-source, documentation was an afterthought. Drop a comment or email bob@werken.com.
TrackBack
