This post originated from an RSS feed registered with Ruby Buzz by David Heinemeier Hansson. Original Post: Test-driven vs test-first development Feed Title: Loud Thinking Feed URL: http://feeds.feedburner.com/LoudThinking Feed Description: All about the full-stack, web-framework Rails for Ruby and on putting it to good effect with Basecamp Latest Ruby Buzz Posts Latest Ruby Buzz Posts by David Heinemeier Hansson Latest Posts From Loud Thinking

I've been a test-driven developer for quite a while, but I haven't really gotten into the religious test-first branch yet. Usually, I'm too impatient. I have a good idea and want to execute on it right away. Then, when I see it in code, I'll come back to do the tests.

I have done short spurts of test-first — some tasks just seem to invite it — but not as a regular approach over a longer and sustained period of time. I want to give that a try. For a month. Where I can't right any code until I've seen a test fail.

It's one of my 43 things.