Back to articles
My team reviews 15 PRs a day at our startup. Nobody burns out.

My team reviews 15 PRs a day at our startup. Nobody burns out.

via Dev.toAditya Agarwal

15 PRs. 0 burnout. Here's what really happened. We used to be 5 eng. PRs were easy. Glance, comment, merge. Then we hit 15. PRs piled up. Eng. waited 2d for feedback. PMs worried. CTO: "velocity?" IRL, most fixes took 2min to review. But 2 days... We tried all. default review necessities. Slack alerts. A Discord script that alerted. No dice. Nothing changed. Because it wasn't the tools. It was the mood. We treated reviews as a favor. Not a must. We made 3 rules. Every PR gets a review in 4 hours. Or it auto-merges. Rule 1/3 Review comments must be actionable. No "consider this." No "what if we tried…" If you comment, suggest a change. Or approve. Rule 2/3 The author owns the fix. Not the reviewer. If you suggest a change, the PR's author does it. I trust you. No ctrl+c, ctrl+v. This is mine now. This was harder than automerging. Sengines love "Let me just fix it." Juniors learn slower then. Also a lot of bugs. Weird, but true. Our bugs dropped. We hit fix reviews cash. No time for flav

Continue reading on Dev.to

Opens in a new tab

Read Full Article
2 views

Related Articles