Code review speed directly impacts team velocity. A long pull request (PR) queue signals slow progress. While code reviews can feel like a chore, they are essential for reducing defects and enhancing code quality. It's also a requirement for SOC2 compliance that at least two people review production code. The author expresses skepticism about AI code review due to poor quality and insufficient nuance. When developers encounter larger tasks that don't fit neatly into a single PR, they often try to cram everything into one request. This leads to complex, unreviewable PRs that are difficult for peers to assess. As a result, the review process can become bogged down. Instead of overwhelming reviewers, the author advocates for stacked pull requests. This approach involves creating multiple smaller PRs that build on each other. Each PR can be merged independently, allowing for more manageable reviews and quicker integration. Managing stacked pull requests can be challenging without the right tools. The author mentions using Graphite, which simplifies the process by managing rebasing and providing clarity on the status of each PR in the stack. This tool has improved the author's workflow, especially during larger refactorings and off-hours coding sessions. Breaking down large tasks into smaller, focused PRs not only helps reviewers but also accelerates overall work flow.