You don’t have time to review every pull request. Here’s how to empower developers to perform code reviews instead.
The transition from developer to team lead can be both challenging and rewarding. You start owning high-impact decisions, mentoring and coaching your peers, and cultivating leadership skills.
Engineers who are new to these responsibilities often make a common mistake: they try to perform every code review submitted by the team. They’re concerned that if they don’t, something will break in production, or code quality will decline.
Reviewing every pull request (PR) isn’t feasible. You have limited bandwidth in your day, and there are many projects that need your attention and priority.