It's fine except that it never happens

I had my encounter with the Exception Monster today.

See, the first thing about our line of work is that there will always be exceptions. Exceptions are those things which nobody wants to really care about, but some stupid user will bring up nonetheless.

Exceptions are those things which some people insist can happen, and will happen, and must happen just to prove that they will and can happen. I have this nagging suspicion that these exceptionistas create the scenarios for exceptions to happen just to prove a point.

See, most people don't want to build complicated system processes just so that you can take care of that once in a year exception. Why? Because most people pay good money for complicated system processes. For that once in a blue moon thing? Don't bother - cross that bridge when you come to it. However, more than one client that I've been to insist on getting that 'bang for the buck', and so exceptions need to be handled.

These irritating exceptionistas don't have half a brain: Its either "Cater for it! I don't care how!" or "Document the exception handling processes, all 20,000 of them". I'm sick of it all - the world isn't ending just because your stupid exception is not being handled. And please wipe that stupid smirk off - I am not really impressed that you're able to find exceptions to throw in my face; I'm appalled that you're not helping with the situation by screaming at me about it.

Anyway, it never ends and that's why I sometimes hate system implementation. No matter what you do, and no matter how much you try, you WILL leave shit behind, and someone else has to clean it up. There are just too many things to juggle, and invariably, some unfinished business gets left behind, tucked nicely away for some unsuspecting soul.

Exceptions are one of those things I'm fond of sweeping under the carpet, so good luck to whoever's looking under the carpet! (you have my sympathies)

(Note: reproduced this post from my post here)