Confession first. My most useful reviews of the last year have all happened in a shared doc, an ADR draft or a twenty-minute call, before anyone wrote a line of the change. The pull requests that followed were mostly paperwork. So when The New Stack published "Move code review before the code" on July 19, framing the pull request as roughly twenty years old and arguing review should move upstream of the code itself, I sat with the headline for a while. It matched what the good weeks already look like on my team.
Where PR review starts to feel late
The pull request has been the CI/CD review venue for so long that the entire pipeline is shaped around it. Draft, push, wait for CI to turn green, request review, negotiate, squash, merge. It has been fine. It has also been the point where I have watched teams argue about names, module boundaries and library choices that were locked in ten hours earlier, when someone ran git add. By the time a diff is on screen, the shape of the answer is already sunk cost. That is the part that stings, and it stings whether the reviewer is a human or a bot.
You will feel this most on the changes that actually hurt: the refactor that touches everything, the migration that has one right answer and three seductive wrong ones, the "small" schema tweak. The comment that would have mattered is the one a reviewer would have made before any typing began, asking what problem you are actually solving and whether this is the smallest thing that solves it. Once the diff exists, that question feels rude. Once you are three days deep, it feels hostile.
