Through an interesting set of circumstances, I have the opportunity to create a really simple build server here on my project team at MS. We're using Windows Services for Unix and writing everything using KSH scripts. Ah, my years of Unix experience coming in handy again :)
Anyhow, the issue here is that my script is now 200 lines long, and I'm trying to put in several different changes to get it finished. But I'm not writing it test first. And because of this, I've got a dozen different changes running around in my head, and it is slowing me down.
Not only does writing code test first let you explore the interface, document the design, and create this safety net of tests, it also forces you to focus on one thing at a time.
I'm not doing that, and it hurts.
-- bab
PS -- Go Cards!!!