3 ms·
The way to do it using TDD is to do your greenfield development to the point of a working solution to elicit your fine-grained requirements, then throw that awa
by bitwize 4y ago
The way to do it using TDD is to do your greenfield development to the point of a working solution to elicit your fine-grained requirements, then throw that away and rewrite it using TDD. The first version is considered a "spike solution" and is not supposed to touch production.
In TDD, all production code must be written against some pre-existing test. Any code which does not meet this criterion is broken.
- ris 4y agoI have never worked with that sort of time luxury.
- _tom_ 4y agoIt's frequently faster. Half-assed designs will cost you time forever.
- ris 4y agoLet's not start throwing pejoratives around, there is nothing half-assed about having an idea how your design will work before you blindly start coding probably-wrong stuff. I've also found having apparent time-luxury to be a rather paradoxical thing, the more of it you have, the more people start spending it by creating bureaucracy and busy-work. It never gets spent how you expect it to be spent.