There should be people whose sole job is to do PR reviews.
The PR reviewers delegate work to programmers, the programmers delegate the work to AI; then, the programmer reviews the AIs work, and the PR reviewer reviews the PR.
Those "architects" or other idea people should be reviewing the PRs and keeping an eye on the whole system. That's their job, right?
Usually the programmers are responsible for their own work, and then also reviewing their own work, which is just weird. The context switching is very draining.
The problem is that PR reviews are viewed as a side-task, and it's a thankless job. The guy who implemented the fancy new feature will be personally thanked by the CEO and taken out to lunch, the PR reviewer who pointed out in the original PR that it would corrupt the database gets a "nice catch" comment, and that's it.
The PR reviewers delegate work to programmers, the programmers delegate the work to AI; then, the programmer reviews the AIs work, and the PR reviewer reviews the PR.
Those "architects" or other idea people should be reviewing the PRs and keeping an eye on the whole system. That's their job, right?
Usually the programmers are responsible for their own work, and then also reviewing their own work, which is just weird. The context switching is very draining.
The problem is that PR reviews are viewed as a side-task, and it's a thankless job. The guy who implemented the fancy new feature will be personally thanked by the CEO and taken out to lunch, the PR reviewer who pointed out in the original PR that it would corrupt the database gets a "nice catch" comment, and that's it.