Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The distinction being that you may feel less productive when doing TDD--but that TDD very obviously yields significant benefits for developers who aren't you. I'm not saying that you should do TDD because it works for me, but I am saying that it very demonstrably does work for me.

If you don't like TDD and don't practice it for this reason or that, that's totally fine. Going out of your way to disabuse junior programmers from using it strikes me as crazy-town, which is kind of the point I'm making here?



> but that TDD very obviously yields significant benefits for developers who aren't you

Isn't this a case of begging the question? It's "very obvious"? It's not so obvious to me. You claim it is "demonstrable," but demonstrate nothing.

I think the idea that writing tests is a substitute for design or documentation is a bad idea that can easily lead someone astray.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: