I'm going to be that guy .... A lot of these rants are about code compiling first time .. Throwing away code you wrote because you didn't need it... Getting in the zone and writing a billion lines before you compile .... Am I the only freaking person here that does TDD ? My rant is wake up people ! People evangelize about it because it fucking works !

I don't, but I like the idea of it. +1 for you.

@emes001 not going to lie, it's hard at the start. You think you are moving slow but it's a short term loss for a very long term gain !

It saves the nerves that would die too

The devs at my place are supposed to use TDD, however it's more like they write them; never run them and then push their code up because it "builds successfully". The QAs then never run them either, and we're left with them breaking in the release branch at the end. Telling them to fix them is a nightmare as well -.-

TDD only works when everyone gives it their 100%.

The disparity between what people consider worth testing and what actually gets tested is one of the most frustrating things also.

Most of the "rants" on here sound like they are coming from people who don't realise they know nothing; they place importance on how complicated/complex their code is and wear their biggest failing as a badge of honour.

Or the good old.

me: "We should add TDD to our workflow."
pm: "Yes, you should, after all the other stuff that you need to do gets done."

I add qunit anyway and add tests as and when I can.

It's easy to start with TDD, but when you inherit a project with absolutely none of that in place and it's been running since before you went to university...