People assume code review is about catching typos. It isn't — the compiler finds those. What review actually catches is one engineer's private assumption about how something works, before that assumption reaches your customers. The side effect matters just as much: after a few months of reviewing each other's work, at least two people understand every part of the system. What's a decision in your business that only one person currently understands?
Was this useful?