Having a team style guide helps a lot with that tendency: you get the argument over with once, team-wide, then write down the conclusion. So during each code re

Having a team style guide helps a lot with that tendency: you get the argument over with once, team-wide, then write down the conclusion. So during each code review it's just a question of: does this match the style guide, yes or no? (Or you can enforce it automatically with tools like ESLint). And then the discussion can focus much more deeply on other aspects of the code.