That’s just horrible programmers in general. Try/catch and release, instead of figuring out what’s wrong. Surely that’s not gonna blow in someone’s face…
I am in the process of fixing a bug at work where pretty much every method has a try(Exception e){…}catch{LOGGER.error(…)}. The method calling my team’s method needs to know when an interrupted exception is thrown. So far I have fixed this in 10 different methods, and we keep finding more. It’s like playing whack-a-mole.
You know at least it printed an error. I hate when things silently swallow errors.
I’m looking at you, Python programmers:
try: <100 lines of nonsense> except: passWe are not savages now we use
with suppress(Exception): > 100 lines nonsenseIs not just because you are right that this is True
That’s just horrible programmers in general. Try/catch and release, instead of figuring out what’s wrong. Surely that’s not gonna blow in someone’s face…
I am in the process of fixing a bug at work where pretty much every method has a try(Exception e){…}catch{LOGGER.error(…)}. The method calling my team’s method needs to know when an interrupted exception is thrown. So far I have fixed this in 10 different methods, and we keep finding more. It’s like playing whack-a-mole.