Small PRs and the Case for Stacking

Faster Code Reviews, Faster Code Shipping with Stacked PRs - Greg Foster

Topic 5 of 12

Published Sep 1, 2025 · Clip 21:02–26:59 (5:58)

Greg advocates for small code changes (roughly 50-150 lines): they get reviewed faster, attract higher feedback per line, are easier to debug and revert, and avoid LGTM-with-no-comments on giant PRs. He acknowledges fixed costs (review wait times, CI, merge queues) tempt engineers to write large PRs, which is why Facebook-descended companies adopted a stacking mentality. Stacking—branching off a branch—parallelizes waiting times so developers keep coding while reviews and tests run.