Re:The Resistance Is Real – Why Side Projects Are So Hard
by bigtunacan on Saturday November 24, 2018 @12:22AM
(#18520582)
Total BS. That is the bill of goods sold by TDD. In TDD the tests become as critical as the code and they are an anchor that weighs you down and slows down time to delivery. It isn't that tests are bad. Build the code, write tests to support anything critical that is a risk, but for the sake of all that is good throw out writing tests first or any notion of 100% test coverage. It's a huge time suck that does not balance out in the end.
[ Parent
| on HN ]
Re:The Resistance Is Real – Why Side Projects Are So Hard
by LanceH on Saturday November 24, 2018 @02:55AM
(#18520991)
I hate on TDD as much as anyone, but there really are occasions for its use. Specifically when the results of working code can't be determined by the person running it. The simplest example I can think of is something like a math library -- if I have code that computes the cosecant of x, I don't really know if it's working or not.
On the other hand, I really don't need controller tests for my 1.0 version -- if they aren't working, it's immediately obvious. Circle back later and throw a test on it to nail it in place if need be, but TDD is absolutely not needed when development is obvious.