Code reviews are not slow.

Bloated pull requests are.

Most engineers think reviews are the bottleneck.

But they’re not.

The real issue is opening one giant PR after three days of coding and expecting instant feedback.

That’s when reviews stall.

That’s when context switching kicks in.

That’s when frustration builds.

Here’s the fix:

👉️ Stack your pull requests.

Instead of one 800-line PR, open 3–5 small ones.

Each builds on the last.

PR 1: Refactor base logic

PR 2: Add validation

PR 3: Implement feature

PR 4: Tests

Now what happens?

✅️ You get feedback early.

✅️ Reviewers don’t feel overwhelmed.

✅️ Changes are easier to reason about.

✅️ Merge conflicts drop.

✅️ Momentum increases.

And unlike pairing, you’re not blocked by calendar clashes or time zones.

You keep moving.

Small PRs create flow.

Big PRs create friction.

Most teams think they have a review problem.

They actually have a PR sizing problem.

Fix that first.

——

💾 Save this for later.

♻ Restack to help others find it.

➕ Follow Petar Ivanov + turn on notifications.