If you read the article, they suggest strongly that it is hard to get a "correct" code review process (perhaps because it encourages the nitpickers, or perhaps for other reasons).
If you've got a bunch of experienced people spending a year on it that can't solve it, perhaps they just can't solve it.
And at that point: What's the difference between something that's wrong, and something that they can't do right?
Good code review is hard. Catching non petty problems is much harder then lengthy obsessing over function names or 'if' vs '?' or whether slightly more or slightly less abstraction or whether two 6 line long function vs one 12 lines long.
> Code review happens through a small window. When reviewing a PR you only look at the fraction of the code that just changed.
Their complaint is that code review makes it easy to miss deviations from global goals & style, not that they nitpick minor presentation issues.
Although I wonder what sftware they are using that would only show them a small fraction of a change…
I.e. all of the code that changed, which is a fraction of the total codebase.