Well perhaps another part of Google&#x27;s code review culture is important, then: proposed changes must be style compliant, must compile, must have tests, and all the tests must pass before anyone will bother looking at them.  If I got a code review (at Google) that was incorrectly indented, there would be a little red chip in the review UI that indicated such style violation, and I would just reply &quot;Please fix&quot; and not look at it again until the next revision.<p>In the absence of a strong style guide and testing culture then I agree code reviews can get bogged down in bikeshedding.  At Google that doesn&#x27;t seem to happen because the style guide for each language is quite prescriptive.  For Go, no change will be reviewed that hasn&#x27;t passed through gofmt, and so forth.  And on the flip side you can have confidence that if your change has gone through gofmt, there&#x27;s not going to be any discussion about the formatting.