This is inane. Logging has been a thing since the stone ages of software engineering. The first thing you do in any environment is set up a debug log of some ki

This is inane. Logging has been a thing since the stone ages of software engineering. The first thing you do in any environment is set up a debug log of some kind. You can make as many error states unreachable as you can, but what the hell do you do when there's an error anyway? Psychically debug the process? edit: how are you going to communicate information as to why something crashed to your colleagues who do not understand certain parts of the system as well as you? A stack trace is not effective at expressing intent. Explaining yourself in logs helps people triage more efficiently.