> Do I need TDD and Code Reviews? Will it pay back all the extra time? There is actually a better question. Why do I need TTD/Code Reviews/Whatever? And the

> Do I need TDD and Code Reviews? Will it pay back all the extra time? There is actually a better question. Why do I need TTD/Code Reviews/Whatever? And the followup question is: Will that give me the benefit I expect? And the final follow up is: Is there anything else that will give me that same benefit. I'm going to say that I like TDD - a lot. But one doesn't just do TDD (to exploit a meme). One does TDD for a reason. If your reason is "because I want to make sure my code works", then I can point to a large number of other techniques that will help as much or better. There are other reasons to do TDD, some of which have very few alternatives. I don't want to write a book on TDD here. My point is that if you are delivering software and being successful, then why would you look for a solution to a problem you don't have? It may be that TDD can help you, but nothing will come of it until you can see the underlying problem for which TDD is your solution. So, yes, I agree. If you see no reason to use TDD, it would be pretty crazy to do it.