Jeff Langr wrote:TDD is a great technique, and yet I don't do it for 100% of my efforts. Do what makes sense.
Tomas Linhart wrote:And from the practical point of view, the last drawback outweighs the benefits for me. Especially at the early stages of a project, when design evolves a lot and the requirements change all the time, it's a double work - write the test and write the code, refactor tests and then the code. Is it really worthy? And is it for everyone and for every kind of project? How to justify the higher costs and slower delivery to the customer (especially when it's internal customer)?
He loves you so much! And I'm baking the cake! I'm going to put this tiny ad in the cake:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton