3 ms·
For you? Or for everyone? The former is a reasonable position, which I assume of you because I think your posts tend to be solid and well-thought-out--and also
by eropple 9y ago
For you? Or for everyone? The former is a reasonable position, which I assume of you because I think your posts tend to be solid and well-thought-out--and also because the latter is demonstrably cracked.
And even if you don't, personally, like TDD, ranting about junior developers "wasting time" using it is some weird stuff. Whose juniors actually want to be writing tests? Most times, you have to hammer it into them.
- emodendroket 9y agoI have no idea what distinction you're drawing or what you think is demonstrable about it. Sorry.
- eropple 9y agoThe 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?
- emodendroket 9y ago> 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.