The funny thing is is that this is part of TDD (and extreme programming) that most detractors of TDD don't understand. I'm talking about the old "but if I don'

The funny thing is is that this is part of TDD (and extreme programming) that most detractors of TDD don't understand. I'm talking about the old "but if I don't know what I'm writing, how do I write a test first?" crowd. Well, the answer is this article. Write a quick prototype to answer unknowns, figure out a general plan, then throw it away and start with a single test. I emphasize "single" because there was that other article that made the front page a couple of months ago where the author described their "new found way" of doing TDD that made them actually enjoy it and then went on to describe regular plain ol' TDD.