5 ms·
This is the exact method I use to teach TDD and it works. It works really well. The article mentions the sunk costs fallacy. This is true. In the workshop I gi
by ryanmarsh 8y ago
This is the exact method I use to teach TDD and it works. It works really well.
The article mentions the sunk costs fallacy. This is true. In the workshop I give you tougher and tougher parameters, shorter and shorter time frames. If your tests aren’t passing you reset to the last commit. You can’t commit without passing tests. People learn, a) write smaller simpler tests, b) code is cheap. The third time you write something you’ll write it faster and better. Better to do that in a tight loop than over a prolonged dev-test-refactor cycle that could last days to years.
You also learn how to refactor in the green. Boy is that a good skill to have.
- microtherion 8y agoBut doesn't the classical TDD process start by writing a test and making sure it fails before the code is changed?
- sdenton4 8y agoGenerally if I make a change and nothing fails, I assume something has gone even more wrong than usual...
- andreygrehov 8y agoheh, i love it. Sounds like a military type of training, lol. I'll give it a try.