TDD is awful if you expect all of the tests you produced during the process to stay static. With care, you can pare down your test suite, or add additional tes

TDD is awful if you expect all of the tests you produced during the process to stay static. With care, you can pare down your test suite, or add additional tests, to be appropriate as a regression suite for the software each time it is iterated to a deliverable state. I actually find TDD helps me design components with fewer responsibilities, almost always as a result of realizing the complexity via writing permutations of test cases. It helps me think about 'what each thing should do' because I don't have that innate ability like some folks. It is especially helpful in pointing out cases where adding a layer of abstraction or introducing subclass variants are beneficial.