Here’s an old but fantastic post about API (mis)design.
To handle an exception, you have four choices, one of which is:
Log it! We bought big hard disks for those servers, let’s use them! Log the exception toString() and print its stack trace, but only if you expect the exception to be thrown over 1,000,000 times each day. Alternatively, if you think that the exception would only occur rarely and that it could indicate a problem worth looking at, just print the exception class name … since stack traces just confuse people!
Hilarious. And, it looks like it’s part 4 of a 7 part series. Via Dejan Bosanac.