4 ms·
"Testing is for sissies! Real Men write correct code." I seriously laughed when I read this. I'm willing to sacrifice the extra couple of inches of programmer
by j_baker 17y ago
"Testing is for sissies! Real Men write correct code."
I seriously laughed when I read this. I'm willing to sacrifice the extra couple of inches of programmer penis size by writing tests.
- rbanffy 17y agoYou can also refrain from writing the bugs ;-)
- forensic 17y agoBut the tests themselves _are_ code. Do you have tests that check the tests? And then tests that check the tests that check the tests? At one point or another you just have to learn to live with bugs.
- rbanffy 17y agoAnd even if all code is provably correct, there is always the chance of a random particle hitting a transistor in the chip and clearing a bit that should be 1.
- forensic 17y agoJust like in math, even if the code is provably correct, there is always the possibility someone screwed up the proof. In the end it always comes down to writing the least buggy software possible and then bug zapping. Having debug tools is smart of course, but TDD goes a bit further than debug tools. When I write unit tests I don't think of them as unit tests I think of them as debugging probes.
- rbanffy 17y agoHave you noticed that there is an uncanny number of downvotes in this whole topic?