3 ms·
>If you're doing TDD (or software development) like this, you're doing it wrong. What do you think is the right way to do it, then?
by meowface 11y ago
>If you're doing TDD (or software development) like this, you're doing it wrong.
What do you think is the right way to do it, then?
- struppi 11y agoMy point is: If TDD leads you to bad design you're doing it wrong. You are probably not listening to your tests and you are probably not taking care to refactor towards a better design. Maybe you are even writing bad unit tests [1]. BTW, if any technique in software development leads you to bad design, and you don't stop and try to improve something, you're doing software development wrong. If a technique does not help you, you have two possibilities: Trying to do it better (maybe with outside help), or trying something different. [1] http://www.makinggoodsoftware.com/2012/01/27/the-evil-unit-test/ http://www.makinggoodsoftware.com/2012/01/27/the-evil-unit-t...
- TeMPOraL 11y agoBut that's a general counterargument for criticism against anything - "if it doesn't work for you, you're doing it wrong"! Ultimately, we're too young a field to be able to replace common sense with a process.