Devs who log exception messages without trace deserve a special place in hell

How about devs who decide to include exception message with stack trace in http response?

@impune-pl Please tell me this didn't happen IRL.

@devdevdev29 It did. The most generic error handler present it application was designed to include exception message and stack trace in http response.

@impune-pl Wow. They go to hell++.

@devdevdev29 nope, somebody asked a very important question during code review - 'won't this help any pentester or hacker?'
So that error handler got rewritten to return extremely generic error message.

My favourite is when the unhandled exception would get perfectly caught, logged, and correlated by default, but someone goes in and adds a catch (exc) { print("error: " + exc.Message) }. No return or throw as a bonus.

git commit -m "added ecception handling"

With minified code what's the point. Everything is line 1 but the column is 554934686987893453

@bashleigh thats why you have .map files in languages that get transpiled or minified.

yeaaa but they don't always get included when uploading...