I haven’t gotten around to writing an article on Test Driven Development yet.  It seems that almost all programmers who write blogs do at some point.  Well, perhaps I won’t need to now, because Chuck over at nothing happens has already written exactly what I would have:

I think the trick is, you can’t do it on purpose.

Write the test when you’re ready; write the test as soon as you’ve figured out how to test what you mean to test. That’s right you Industry Thought-Leaders, you hear me? I’ll test when I’m ready, not when you tell me to.

Now that you’ve had a small taste, go read it.  I won’t be writing anything better on this subject, certainly not in the foreseeable future.