Time for a Break

This is for all the developers/software administrators out there. Sometimes, as much as they try to help, application errors are entirely useless. "Object reference not set to an instance of an object" is a favourite. Also good is the simple and infuriating "unexpected error". Perhaps the very best is "please contact your system administrator", when you ARE the system administrator, and you have no idea what's going on. Classic. ~C Be sure to like us on Facebook and follow us on Twitter, eh ;) Share/Bookmark

6 thoughts on “Time for a Break

  1. A computer at work before they upgraded to new ones used to often have a Fatal Exception. That always sounded bad

  2. This is the cue to take a break or lunch.

  3. “Object reference not set to an instance of an object” is just C++ or Java’s equivalent of “undeclared variable”. That should get caught at compile time.

    These are largely errors thrown by compilers, not application developers. That you’re seeing them at all means that the developer wasn’t trapping exceptions properly.

  4. This is how Actionscript handles it’s error trapping. “Sorry, you dumb enough to program AS2, then you deserve to suffer.”

  5. At work, since our software has multiple users accessing a database we get people constantly sending us bug reports for “OptimisticConcurrencyException”.

  6. If it wanted to be meaner it would probably laugh at you too!

Leave a Reply

Your email address will not be published. Required fields are marked *




* Copy this password:

* Type or paste password here: