Development tools ultimately are there to help the developers. For teams with a mix of abilities, something like gerrit can make sense where approval is needed

Development tools ultimately are there to help the developers. For teams with a mix of abilities, something like gerrit can make sense where approval is needed before a merge to avoid total chaos. For a group of experienced developers, approval is a very expensive delay, and merging should be allowed first and review done in parallel. Where I work the only people who commit are experienced developers, so the whole +2 gerrit thing is rather pointless, especially since jenkins does syntax-checking. You might spot the occasional "typo" in a commit, but are you really going to tell the local language expert or framework author they're wrong about anything else, when your opinion carries the same weight as theirs?