TDD does yield very good things, and I find the arguments against it to be generally pretty weak.

At the same time, I don’t see a lot of (very smart) people adopting TDD, and even those that do seem to want to abandon it, even when they will admit they should probably be doing it.

Even when teams are encouraged (or even pushed) to adopt TDD, it seems to be difficult to stick with. I put myself in the the same camp, frankly: I see the positive results, yet I continually fight the urge to cut corners.

Given that it’s full of goodness, as it were, what’s the problem (or problems) preventing more widespread adoption? Why do I have to convince myself that I need to keep doing TDD, given that there are so many benefits, and I can’t put my finger on many shortcomings? I’m not the only one, clearly, so the post was an attempt to work through some of that, and engage a bit of group-think.

TDD is great, but it confuses you. It confuses you because it is so great you do not understand why everybody would be doing it.

Did I get that right? Sounds like we moved off into marketing land there, dude.

How about “TDD is great because on this project I’m on we’re delivering more code faster with less defects than we would have done otherwise”

Then build a supporting case for that.

Sorry for busting your chops, Keith! I just wrote you a glowing review on LinkedIn, and had to let out my crankiness somewhere(grin) Somehow your article set off my BS detector, but it’s been needing some work lately, so hard to tell if the alarm was real or not. I might need to change the batteries.