4 ms·
It's because the real conflict (up front design vs finding as you code) is hidden by the small quirk of writing code with pen and paper. Rename the article "why
by Zababa 5y ago
It's because the real conflict (up front design vs finding as you code) is hidden by the small quirk of writing code with pen and paper. Rename the article "why TDD is useless", change the angle a bit and you'll create way more controversy.
- UK-Al05 5y agoDon't think it conflicts that much with TDD. The test is the problem statement, or maybe a theorem. You then need to figure out how to solve/prove it. You can do this on paper then type it in or directly. It doesn't really matter. When the test goes green you know you've solved it.
- Zababa 5y agoThat's a good point, you could indeed run the tests in your head. I think I can still save this though: this would prove that you only test for what you think about, and thus the existence or the absence of a test doesn't affect the development at all. Which could be countered again by property-based testing, but this one won't work in your head or one paper.