How to Review Code Kindly (and Still Catch the Bugs)
Kind review is specific review. What to check in a PR, how to word comments people can act on, how to label nits and blockers, and what the data says about PR size.
Blog series
Practical habits for code review, pull requests, feedback, and mentoring that improve the work without losing care for the people doing it.
Kind review is specific review. What to check in a PR, how to word comments people can act on, how to label nits and blockers, and what the data says about PR size.
Kind and nice aren't the same. How kind engineers give honest feedback, run blameless incidents, say no early and back their teammates, plus the research behind it.
One change per PR, a title that says what it does, a description with the why and a test plan, and a self-review before you ping anyone. The author’s side of review.
Feedback runs both ways. The SBI model, when feedback makes work worse, how to make praise useful, and how to hear hard notes without getting defensive.
Mentoring is a skill you can practice: pick work one step past someone's reach, say your reasoning out loud, then pull your support back one rung at a time.