9 ms·
And yet, at least for the quoted part, he is right. It requires some massive balls to deploy code to production while not even seeing if it works for any case.
by Dudeman112 5y ago
And yet, at least for the quoted part, he is right.
It requires some massive balls to deploy code to production while not even seeing if it works for any case.
If the answer to "how do you know it works?" is "trust my judgement bro" then I will not, in fact, trust their judgement.
I do agree he has a finger in the zealotry and he should probably have modulated how he expressed himself.
- marginalia_nu 5y agoYou know, they sent people to the moon using software written before the unit test paradigm.
- rootusrootus 5y agoWay, way back in the day, one of the best applications I've ever written had no tests. That application is probably in use today, in fact, even though its life is measured in decades. My takeaway is that tests are important, but good code is still more important.
- marginalia_nu 5y agoWhat I really wanted to say is that there is more than one way of knowing whether code works. Unit testing is one paradigm. Just because Uncle Bob, seller of unit testing software and TDD-books will hear of no other doesn't mean that this is the One True Way.
- Dudeman112 5y agoThere's more to testing than unit testing. I haven't actually read his site, I'm going by what was quoted. Might be that he meant "unit tested" when he said "tested", I guess.