You could look at this through the lens of computing, which it arguably is. Consider physics as the BIOS/firmware for the machine code of the universe, at some fundamental layer, then layer on ever-expanding complexity of programming languages on top of that. Reaching human "codes of conduct", one could consider a division of wetware (biology) and the epiphenomenon of culture, etc., as operating systems and applications.
Whatever code(s) you are going to operate under will still be running on the prevailing operating system. And, unless you've written the exceptions for it, errors are going to cause crashes. It's natural to error-correct and "debug" your behavior, if one wants to find the means to operate and run their code. Either that, or find a different platform or OS you're more compatible with.
All the "errors" are really "consequences" and making "exceptions" and "debugging" is how or if you want to learn and adjust. Do or don't. Compute or don't compute, that is the question: Whether it is nobler in the running of your program to suffer the slings and arrows of outrageous exceptions, or to take arms against a sea of errors and by debugging, end them?
Thrall to the Wire of Self-Excited Circuit.