Apply a tailored “ready for review” checklist to ensure a PR is in a state where detailed code review will be productive.

Tests should be included in the same pull request as the code changes they test; this provides verification, eliminates risk, and guarantees no-fuss rollbacks.

Here are the slides and transcript for a talk I gave at a Meetup event on April 22 2025.

When a PR can’t be small, it’s on the author to keep it reviewable—because reviewable PRs lead to better code.

For an effective and efficient code review, focus on understanding the problem, gathering context, and ensuring basic functionality.

Here are the slides and transcript for a talk I gave at a Meetup event on February 18 2025.

When approaching a code review, determine whether the pull request is reviewable before diving into the actual code.

By sharing in-progress work, you can invite early feedback, integrate with CI tools, and foster trust and transparency within your team.

Early code reviews, when used thoughtfully and aided with clear communication, save time and improve team morale.

After I submit a PR for review, it remains my top priority until it's fully integrated into the codebase.

In this post, I share five key techniques that help make my PRs a pleasure to review.

Software development teams can save time and avoid frustration by establishing a shared definition of "ready for review."

Every software developer should establish their own definition of 'ready for review.' Doing so will help them produce high-quality output.