The Startup
Published in

The Startup

4 Rules of Thumb for Providing Effective Code Review Feedback

image by Manu Cornet under Creative Commons license

The worst case scenario for a peer code review is when each developer thinks the other will look at the code closely. This happens in real life, more often than you would think. How do you go about ensuring this does not occur? A large part is establishing a healthy code review culture, where the roles and expectations of the parties are known.




Get smarter at building your thing. Follow to join The Startup’s +8 million monthly readers & +756K followers.

Recommended from Medium

What We Learned Using Elasticsearch as a Time Series Database

ByteDance to launch e-finance application “Fang Xin Hua”

Monika v1.6.2 has been released!

H12–891_V1.0-ENU HCIE-Datacom V1.0 Exam Questions

WhiteBIT Supports Hamedan Hardfork

Bitmates January Devlog

Android development tips — Part I

Using classic Esri Story Maps URL parameters

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Kendra Curtis

Kendra Curtis

Ex-Googler with 20+ years of Software Engineering Experience.

More from Medium

Experienced Developers, Ask These Interview Questions to Reveal Toxic Workplace

You can’t review every Pull Request. Do these 7 things instead.

Software Estimation: A Two Dimensional Approach

How Does a Daily Standup Last Forever?