> catching every exception and wrapping Our company introduced Q into our review process and it is insane how aggressive Q is about introducing completely inan

> catching every exception and wrapping Our company introduced Q into our review process and it is insane how aggressive Q is about introducing completely inane try catch blocks - often swallowing exceptions in a manner that prevents their proper logging. I can understand wanting to be explicit about exception bubbling and requiring patterns like `try { ... } catch (SpecificException e) { throw e; }` to force awareness of what exceptions may be bubbling up passed the current level but Q often just suggests catch blocks of `{ print e.message; }` which has never been a preferred approach anywhere I have worked. Q in particular is pretty silly about exceptions in general - it's nice to hear this isn't just us experiencing that!