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.

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

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.