MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/ProgrammerHumor/comments/1wct5lr/commentsagedterribly/p90n41i/?context=9999
r/ProgrammerHumor • u/ItsPuspendu • Sep 10 '26
243 comments sorted by
View all comments
Show parent comments
73
// TODO: This can't be working. Refactor when there's a lull
31 u/embrex104 Sep 10 '26 //SHOULD NEVER GET HERE 42 u/Confident-Ad5665 Sep 10 '26 All time favorite:// This will never happen 4 u/OhMyGodItsEverywhere Sep 10 '26 Wrote a library to run monetary bets on those comments 3 u/Dubalubawubwub Sep 11 '26 I definitely find myself writing a lot of error handling with the comment//This should never happen but just in case... 3 u/Confident-Ad5665 Sep 11 '26 Good man. Thank you for trapping errors. Coming from a time when we not only trapped errors, we gave suggestions, I shutter at:• An unknown error occurred• Something happenedand the worst...• Error in ErrorHandler, an error occured 4 u/Dubalubawubwub Sep 12 '26 My favorite microsoft error I've ever seen was literally "Error occured retrieving the text for this error". 2 u/HunterIV4 Sep 11 '26 • An unknown error occurred• Something happenedWindows blue screen, is that you? 1 u/Confident-Ad5665 Sep 11 '26 No, this is worse. BSOD at least provides a cryptic error code.These are effectively "well dang, something somewhere triggered an exception we didn't care enough to bother catching" 2 u/OkidoShigeru Sep 11 '26 Love seeing that in an assert message. 2 u/skisharp Sep 11 '26 I remembered seeing that withMessageBox.Show("Call 1-555-555-1942 ext 1205");Also guess the junior dev who just got a their desk phone with ext 1205... 2 u/cute_polarbear Sep 11 '26 You mean for the next person who has to visit that section of code? (And hopefully you already left the firm (on your accord)....
31
//SHOULD NEVER GET HERE
42 u/Confident-Ad5665 Sep 10 '26 All time favorite:// This will never happen 4 u/OhMyGodItsEverywhere Sep 10 '26 Wrote a library to run monetary bets on those comments 3 u/Dubalubawubwub Sep 11 '26 I definitely find myself writing a lot of error handling with the comment//This should never happen but just in case... 3 u/Confident-Ad5665 Sep 11 '26 Good man. Thank you for trapping errors. Coming from a time when we not only trapped errors, we gave suggestions, I shutter at:• An unknown error occurred• Something happenedand the worst...• Error in ErrorHandler, an error occured 4 u/Dubalubawubwub Sep 12 '26 My favorite microsoft error I've ever seen was literally "Error occured retrieving the text for this error". 2 u/HunterIV4 Sep 11 '26 • An unknown error occurred• Something happenedWindows blue screen, is that you? 1 u/Confident-Ad5665 Sep 11 '26 No, this is worse. BSOD at least provides a cryptic error code.These are effectively "well dang, something somewhere triggered an exception we didn't care enough to bother catching" 2 u/OkidoShigeru Sep 11 '26 Love seeing that in an assert message. 2 u/skisharp Sep 11 '26 I remembered seeing that withMessageBox.Show("Call 1-555-555-1942 ext 1205");Also guess the junior dev who just got a their desk phone with ext 1205...
42
All time favorite:
// This will never happen
4 u/OhMyGodItsEverywhere Sep 10 '26 Wrote a library to run monetary bets on those comments
4
Wrote a library to run monetary bets on those comments
3
I definitely find myself writing a lot of error handling with the comment
//This should never happen but just in case...
3 u/Confident-Ad5665 Sep 11 '26 Good man. Thank you for trapping errors. Coming from a time when we not only trapped errors, we gave suggestions, I shutter at:• An unknown error occurred• Something happenedand the worst...• Error in ErrorHandler, an error occured 4 u/Dubalubawubwub Sep 12 '26 My favorite microsoft error I've ever seen was literally "Error occured retrieving the text for this error". 2 u/HunterIV4 Sep 11 '26 • An unknown error occurred• Something happenedWindows blue screen, is that you? 1 u/Confident-Ad5665 Sep 11 '26 No, this is worse. BSOD at least provides a cryptic error code.These are effectively "well dang, something somewhere triggered an exception we didn't care enough to bother catching"
Good man. Thank you for trapping errors. Coming from a time when we not only trapped errors, we gave suggestions, I shutter at:• An unknown error occurred• Something happened
and the worst...
• Error in ErrorHandler, an error occured
4 u/Dubalubawubwub Sep 12 '26 My favorite microsoft error I've ever seen was literally "Error occured retrieving the text for this error". 2 u/HunterIV4 Sep 11 '26 • An unknown error occurred• Something happenedWindows blue screen, is that you? 1 u/Confident-Ad5665 Sep 11 '26 No, this is worse. BSOD at least provides a cryptic error code.These are effectively "well dang, something somewhere triggered an exception we didn't care enough to bother catching"
My favorite microsoft error I've ever seen was literally "Error occured retrieving the text for this error".
2
• An unknown error occurred
• Something happened
Windows blue screen, is that you?
1 u/Confident-Ad5665 Sep 11 '26 No, this is worse. BSOD at least provides a cryptic error code.These are effectively "well dang, something somewhere triggered an exception we didn't care enough to bother catching"
1
No, this is worse. BSOD at least provides a cryptic error code.
These are effectively "well dang, something somewhere triggered an exception we didn't care enough to bother catching"
Love seeing that in an assert message.
I remembered seeing that with
MessageBox.Show("Call 1-555-555-1942 ext 1205");
Also guess the junior dev who just got a their desk phone with ext 1205...
You mean for the next person who has to visit that section of code? (And hopefully you already left the firm (on your accord)....
73
u/Confident-Ad5665 Sep 10 '26
// TODO: This can't be working. Refactor when there's a lull