Error Handling Strategies

Yes, and it's ironic that there's an error in the error handling routine :D

That's the point, forcing to handle errors doesn't force to do it properly.

Sometimes the "error" is more like, "this is a case that logically could happen but I'm not going to handle it, nor refactor the whole program to stop it from being expressable"

There are other ways of handling errors besides exceptions.

probably what happens when everyone codes using the 'Don't ask for permission, ask for forgiveness later' principle when handling errors

You do not handle errors by randomly segfaulting.

That’s not ignoring errors, it’s explicitly choosing what to do in case of one (crash).

"Error handling is just expensive code bloat" -- PHB

Usually, you don't have any good thing to do with the error, so keeping it around just makes your code worse.

IMHO if error handling is rocket science, the error is you