I have been work at a company for about a year now and i havent seen an exception correctly handled ONCE.

Classic 🤮

I've been called to help with so many bits of debugging where it "just wasn't working but there's no error message", and it turns out the above construct was masking a NullPointerException or similar...

Static code analysis tools can help ensure this is stamped out, if you want to push that to the higher ups.

Since I'm doing mostly c I don't handle exceptions that often. On my java project that fetches data from the internet the lib I use often throws exceptions because the http status code was 503. I know that's because website owners don't like people like me. I simply try again a few times. Is that a thing to do or would it be better if I did it another way. But yes, simply handling every exception by doing nothing is bad... And ugly... And I hope these people will die one day because they couldnt fix a bug because they didn't print an error.

Dont worry everyone i fixed it!

// This should never happen

https://github.com/search/...

Pretty sure that's what Dynamics CRM does for just about everything...

Legit laughed, sucks mate but I'm working on a JS codebase with multiple console logs and call backs.

Saw this rant on 49, couldn't bare that number, maybe OCD, so 50 it is, looks good now

@nothappy true hero

@Zhorian to be honest, Dynamics CRM has a quite verbose logging, if you activate it.

@geaz rolled my own in the end. Gimme angular development any day.