Due to the nature of my work I'm often in a position to write, deploy and then maintain systems that are running my code and generally have to play the part of

Due to the nature of my work I'm often in a position to write, deploy and then maintain systems that are running my code and generally have to play the part of top tier support for the entire stack. The more that this has become my reality, the more I care about actually producing worthwhile errors. I'm not at all bothered that 70% of my code is error case management with some liberal sprinklings of context into those values. At this point, I see straight through them in my code, to the point where I'm actually going to be confronted with an error, bug or emergent system case and I'm going to be exceptionally pleased that I put so much effort into actually managing these errors correctly and not just punting them up through a common and often cryptic common error handler case with most of the useful context about the detailed error environment now missing.