I Switched to Stacked PRs. My Team Reviews Code in Hours, Not Days.

I used to open PRs with 800 lines changed and wonder why my team took two days to review them. I am one of the founding engineers in a 15-person startup. We work quickly. There is no review team available or asynchronous reviews that can take days due to different time zones. If a PR takes two days, the whole pipeline for that feature stalls. The Guilt-Driven Scroll It wasn't waiting the two days that bothered me most. It was the fact that when the review finally did come in, 200 lines were read thoroughly, and the rest got the "looks good to me". Every time. This is not reviewing, it is trying to get out of guilt by scrolling. What Stacked PRs Actually Look Like I started using stacked PRs about a year ago. I wouldn't go back. The concept is simple: instead of one giant PR per feature, you break it up into a chain of small, dependent PRs that build on each other. Sounds nice in theory, but how does it actually work? Let's say I am building a new data pipeline and I have to update the