3 ms·
I agree with you about the TDD presentations. They usually show exactly the trivial cases that could just as well be proved. But at the end of the day the quest
by fauigerzigerk 19y ago
I agree with you about the TDD presentations. They usually show exactly the trivial cases that could just as well be proved. But at the end of the day the question is which camp has empirical proof of being able to improve software quality in real world projects. My feeling is that the "correctness proof" camp doesn't have much to show in terms of progress recently. What we're seeing instead is a useless proxy fight between dynamic typing versus static typing proponents about stuff that can just as easily proved as it can be tested.
- boucher 19y agoI agree that this particular argument is pretty pointless, and I even believe that there are plenty of examples of people programming with TDD and having great results. My only problem with the TDD paradigm is that it doesn't work with the way I think about software. It isn't so much about having a formal correctness proof, but when I'm writing code, its incredibly more valuable to me to think it through, reason about the various inputs and outputs, and convince myself that it is a correct solution. And although I usually don't, I see the value in writing tests to verify some of the assumptions you made. I don't, however, see the logic in starting from a set of tests (especially ones that can't possibly know about the specific "pressure points" of the code you will eventually write) and then deriving the solution. But that's just me, and as they say, different strokes...