[Tyguy7]

Agreed. I have only used TDD once as a front-end web developer, and I've found that I do struggle with the practicality of it. I spent half my time managing and maintaining my tests. When I did the math, It seemed that all that extra time spent was more than It would have taken to simply chase down bugs that would have arisen in a non-tdd environment. It just seems to take more time than is practical. Especially in agile startups.

[atilaneves]

Perhaps. The difference is that in one case you'll have the machine automatically tell you when and why your code stops working because of a regression, and in the other you have no clue until the customer hits it. It's not only about proving it worked once, it's about proving it with every commit.

[ZeroGravitas]

Is the only metric your time spent preventing/chasing bugs? What if those bugs get out to the customer and impact them?

[jpindar]

There's a difference between TDD and having unit tests!

[CmonDev]

Actually in this case he seems to be past his personal TDD hype peak: "... a proponent of the selective use of Test-Driven Development."

Hopefully this will become a mainstream thought. Then maybe we will fix the legacy browser languages problem. Man can dream...