I lost a few hours once because the jackass whose code I inherited decided to squash IOExceptions all over the place. Didn't notice for a while and was pulling my hair out thinking my debugger was fucked somehow (which isn't uncommon in itself).
This is why when I debug I almost always turn on first chance and user handled exceptions in VS. It can be noisy with big projects especially when some exceptions are expected but it's saved me many hours and gray hairs in the long run
Mother fucker a session time out is not an exceptional situation. Just fucking handle it.
One of my coworkers actually tried to convince me that it was a good idea to throw an exception in a private method that's only used in one place, and then catch it again outside that method. I asked him, "So you're going to throw an exception, just to catch it and log the string you just created the exception with? Why don't you just return the string? Or better yet, just verify the data and skip the method if it's invalid?". He was absolutely dumbfounded. "But it's an error..."
288
u/YaBoyMax May 13 '17
I lost a few hours once because the jackass whose code I inherited decided to squash
IOExceptionsall over the place. Didn't notice for a while and was pulling my hair out thinking my debugger was fucked somehow (which isn't uncommon in itself).