The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
(Score: 0) by Anonymous Coward on Wednesday May 30 2018, @10:05PM
by Anonymous Coward
on Wednesday May 30 2018, @10:05PM (#686511)
I don't know if you are serious, and I hope you aren't.
But, I am sad to say I have seen this behavior in legacy code my team has had to maintain. When I asked devs who had been here a long time why there were so many empty catch blocks in the code, they said former management wanted to reduce the amount of errors the service produced, and gave a ridiculous timeframe to get the work done. The only solution was to remove the logging statements in the catch blocks. This is a true story. :(
(Score: 0) by Anonymous Coward on Wednesday May 30 2018, @10:05PM
I don't know if you are serious, and I hope you aren't.
But, I am sad to say I have seen this behavior in legacy code my team has had to maintain. When I asked devs who had been here a long time why there were so many empty catch blocks in the code, they said former management wanted to reduce the amount of errors the service produced, and gave a ridiculous timeframe to get the work done. The only solution was to remove the logging statements in the catch blocks. This is a true story. :(