4 ms·
There is the spirit of "divide and conquer" in this method. Which thing is good. However, I do not know how to follow this advice: "DO NOT PERFECT AS YOU GO. T
by begueradj 2y ago
There is the spirit of "divide and conquer" in this method. Which thing is good.
However, I do not know how to follow this advice: "DO NOT PERFECT AS YOU GO. This is a huge and common mistake" because, when you develop something critical and apply TDD, testing actually is a synonym of perfecting your approach to solving an issue. Not to mention that testing comes before code itself: it pushes you to think carefully, and come out with the best strategy before iterating any further.
- mbivert 2y agoWell, for example, one could not systematically test everything in the first pass but a few things, and then come back later to write more tests. The first draft can, should even, be sketchy: it doesn't have to work all the way through; one can think of it as a prototype to help you understand the problem better[0]. It can even be discarded, for example if it's too far away from what is actually needed. In that setting, TDD might be more suitable for a second or a third pass, once you have a solid grasp of the code's structure. [0]: https://en.wikipedia.org/wiki/The_Mythical_Man-Month#The_pilot_system https://en.wikipedia.org/wiki/The_Mythical_Man-Month#The_pil...