Fix code review bottlenecks by doing like private torrent trackers and only allowing people to get their PR reviewed if they reviewed enough PRs beforehand to keep their ratio high enough.
@mononcqc I’ve long felt the bottleneck to code review is most often something earlier in the process. Architecture discussion, definition of done, scope, backlog grooming, product, sales…
With all that, your suggestion may address the rockstar developer problem. We deal with what we can when we can.
@mononcqc FRRouting requires PRs to be reviewed by someone with a different affiliation (company, generally). Social pressure on a corporate level, basically. You can even explain it to your suits in finance, i.e. why you need to spend the time reviewing other companies' shite. Works quite well!
