No! Terrible advice. Good luck trying to figure out why component X has stopped working without logs of any kind, not even a timestamp of when it stopped work

No! Terrible advice. Good luck trying to figure out why component X has stopped working without logs of any kind, not even a timestamp of when it stopped working. Logging does not make any sense? That's just polemical. His examples are unrealistic and can be taken apart quickly. Can I make bad states unreachable? No, I can never know all paths to failure, and perhaps I don't care. I can't complete a write, I don't care if storage is full or I don't have perm but I want to know that my write did not complete. Further along he goes on to advocate for logging systems. And "business monitoring". What does he think drives these "business monitoring" thingy? Quick notification -- what's that? Like, an output of some kind, denoting a state? I think we call that logging. Log everything, make sure it goes somewhere you can look at. Logging but not collecting is as good as writing to /dev/null.