Code reviews are a waste of time. All the (wrong) design decision have been already made and it will be wasting everyone's time to start resolving those in the PR. The correct thing to do is collaborate early on before the pull request and the actual code review would be only a formality where we check that we don't have files we didn't intend to commit. Reasonable test coverage and static analysis should be relied on.
Another way of seeing it could be the: author of the code shares all valuable insights including documentation with the team so that new concepts get to know and the knowledge is spread immediately with the appearance in the code base. That is very valuable and helps to avoid knowledge silos amount a team.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.