4 ms·
TDD is fine when you have a specification to work to. A lot of software development in the real world is quite "experimental". Requirements are poor so devs nee
by collyw 6y ago
TDD is fine when you have a specification to work to. A lot of software development in the real world is quite "experimental". Requirements are poor so devs need to provide what is essentially a prototype and receive feedback until it is good enough.
- schanq 6y agoAgreed and that’s what spiking is for! Once you have an idea of the solution then you can implement properly with TDD, which generally results in a much better design than just going with the original spike. However, I find it bizarre that many engineers think unit testing is beneath them. I can understand that people find it difficult to stick to the test first discipline. But it’s crazy to me that you wouldn’t want to write tests at all.. I feel so much happier with the additional protection.