If TDD is design, it's a stupid strategy. The only thing you'll get out of it is code that can be easily tested, not the one that is easy to use or robust. If y

If TDD is design, it's a stupid strategy. The only thing you'll get out of it is code that can be easily tested, not the one that is easy to use or robust. If you want good and robust code, aim for good and robust code, not for some vaguely-related proxy. Automated tests, when they were invented, were about not introducing regressions, not about influencing a design.