5 ms·
I'm really rather surprised that we're still talking about "is TDD worth it?" To me, it's a bit like asking, "is OO..." or "is functional..." or what have you.
by moron4hire 13y ago
I'm really rather surprised that we're still talking about "is TDD worth it?" To me, it's a bit like asking, "is OO..." or "is functional..." or what have you. I should hope any developer I work with would know TDD and would know when to use it and when not to use it.
TDD is a style of development that emphasizes simplicity of code interface and accuracy and precession of results. However, not all project have these three things as requirements. In those areas where one has a distinct model of their problem, TDD excels and will save you tons of time over a long run of forcing you to consider corner cases and avoiding breaking existing code with new changes. It's excruciatingly difficult to test things in the fuzzy logic and statistical realms, as you always run the risk that your artificially generated data set does not reflect reality very well.
And none of this should be news. This should be standard information about TDD. It should be clear that TDD is a tool that makes sense when TDD makes sense. Just as it doesn't work well to write an OO abstraction of general-purpose sorting algorithms, and it doesn't work well to write a purely functional simulation of a car, so does it not work well to TDD certain things.