News for hackers. Stuff that matters.
Re:Code reviews aren’t just for catching bugs by qaq on Thursday May 12, 2016 @03:44PM (#11686172)
You can often have 100% test coverage and critical change code reviews, for about same cost as doing code reviews for each commit.
Re:Code reviews aren’t just for catching bugs by renku on Thursday May 12, 2016 @04:32PM (#11686548)
It's hard to decide which are the critical changes. Even a single line change can have major consequences - where do you draw the line...

I guess both 100% code review coverage and 100% test coverage are extremes that one shouldn't worry too much about. But my suspicion is that 100% test coverage can do more harm than reviewing of each commit.

Re:Code reviews aren’t just for catching bugs by qaq on Thursday May 12, 2016 @04:47PM (#11686659)
Obviously depends on a project and team size. In a reasonably sized team a team lead would be the one to draw the line.