"It is unprofessional to release code that you are not sure if it will work or not. Know that it works." The cost for making software that you know works, for

"It is unprofessional to release code that you are not sure if it will work or not. Know that it works." The cost for making software that you know works, for the formal definition of "know"[1] is very, very high. That level of quality is usually reserved for space shuttles and similar. TDD makes software as good as the tests you write. No more, no less. It can be a great aid in producing better code, and better tested code, but in the end all software development is a trade-off between time spent and quality. You have to decide where the line for "good enough" is. TDD itself doesn't magically move this line to "perfect" without incurring a corresponding cost in development time. [1] A knows B iff B is true and A believes B and A has good reason to believe B.