You Developers Need to be Fucking Shot
This is the second time in two days I've run into an issue where the error message tell me something of little value. When you throw an exception, include information about what caused the exception. Yesterday, I got burned by Oracle which threw the exception "Table or View does not exist." Thanks for the help, I guess I'll just find out which of the 50 tables I was referencing is missing through process of elimination. WHICH TABLE WAS IT?! I can just imagine the code next to where the exception gets thrown, the tableName variable sitting within local visibility.
Similarly, I got burned today by Crystal Reports. "Missing parameter value". I didn't write this dumb report and there's like 150 parameters in the report. How do I know which one didn't get supplied. ARGH! I'm fairly certain the answer was right next to the code where you threw the exception. Now instead of resolving the issue in a matter of minutes, the solution may take me up to an hour.