> Because I think the shape of this code is pretty good. That's the wrong attitude. Nobody commits code they don't think is good, but unless you measure "good"

> Because I think the shape of this code is pretty good. That's the wrong attitude. Nobody commits code they don't think is good, but unless you measure "good" objectively and thoroughly there can always be problems you don't notice. The entire point of the article is that there ARE bugs buried in all that noise, and that you can surface and prevent them from being Future Wink's problem by spending an hour today to fix the tooling. For 800 lines it should take you far less than an hour, and if there is a "TON" of complaints there are probably one or 2 real bugs. Multiply that by 10k LOC and you start to realize the scope of the problem. Take the pain, fix it today while you are just at 800, so when you're 1000 or 5000 it's 5000 lines of better code.