NEW REFCARD

Code Review Patterns and Anti-Patterns

The code review process is vital to releasing products and updates that meet and exceed expectations. Ideally, your team is working together, making small and frequent commits, and requesting interim reviews for larger projects. But patterns of heroism, over helping, self-merging, and rubber stamping can be symptoms of a review problem that can lead to tech debt down the road. Learn to recognize common code review patterns and get tips on how to manage them.

Download Refcard

 

Learn to Recognize and Manage These Patterns
 

Long-Running PRs

Old pull requests (PRs) can quickly become irrelevant, especially in fast-moving teams. To reduce the time PRs are open, set expectations around time to first comment and time to resolution.

Download Refcard

 

Heroing, Over Helping, and Self-Merging

Instead of allowing engineers to get into the habit of last-minute saves or acting as the Lone Ranger during code review, encourage a culture of getting feedback early and often throughout the process.

Download Refcard

 

"Just One More Thing"

Late arriving PRs can point to process and culture issues that create an unpredictable workflow. Long-term solves include eliminating bottlenecks and process issues early in the engineering and review process.

Download Refcard

 

BROUGHT TO YOU IN PARTNERSHIP WITH