The real cost of ignoring error handling
The version of this that works is simpler than the version most people imagine. Nobody bills you for neglecting error handling. The cost shows up somewhere else.
Most development decisions are really maintenance decisions wearing a different hat. Anything you cannot measure here, you are deciding by taste, which is fine as long as everyone knows it.
Where the cost lands
- Time spent on work that should not have been necessary
- Enquiries that quietly never arrive
- Swallowing errors silently is how bugs survive for months
- Rework, once the problem is finally visible
Fail loudly in development, gracefully in production. Getting it slightly wrong is survivable. Ignoring it entirely is not. It is the sort of thing that looks like polish right up until it costs you an enquiry.
A reasonable first step
Log enough context to reproduce without guessing. None of that requires a large budget, only a decision and someone to own it. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.
In practice
Code gets read far more often than it gets written, and usually by someone with less context than the author had. Three things worth confirming about error handling before you move on:
- Someone can say what the current setup is without going to look
- Swallowing errors silently is how bugs survive for months — and you know whether that is true here
- There is a way to tell whether the last change to this helped
If you are not sure where your systems currently stand on this, it takes us about an hour to find out.