The good news is, it does increase the output of less-experienced developers. The bad news is, it also increases the output of less-experienced developers.
We use a fairly standard code review process: make a PR, have it pass CI/CD tests, have other developers review, and merge into main if approved. The problem is that we are getting a larger volume of PRs to review and it's beginning to cut into the productivity of more senior members of the team.
How do you handle this increase in PR review activity?
codingdave•7mo ago
I've seen teams try too hard to keep the seniors "productive", and they just end up with the juniors/mids bottlenecked because their code never gets reviewed. So if you measure productivity by overall flow of code through your process (think Kanban, not Scrum), you'll be able to resolve this conundrum.
lenerdenator•7mo ago
codingdave•7mo ago
lenerdenator•7mo ago
We're doing more of the latter suggestion, though that is coming with more "reviewer's burnout". We are trying to deal with it through smaller PRs, but then of course, you fall back to the problem of having more of them.