I've seen projects where management had rules like "you must have 70% code coverage before you check in". Which is crazy, for a lot of reasons. But the develop

I've seen projects where management had rules like "you must have 70% code coverage before you check in". Which is crazy, for a lot of reasons. But the developer response in a couple cases was to puff the code up with layers of fluff that just added levels of abstraction that just passed stuff down to the next layer, unchanged, with a bunch of parameter checking at each new level. This had the effect of adding a bunch of code with no chance of failure, artificially increasing the amount of code covered by the tests (which, by the way, were bullshit). I got to rip all that junk out. It ran faster, was easier to understand and maintain, and I made sure I never, ever worked with the people who wrote that stuff.