The Art of Giving and Receiving Code Reviews Gracefully
summary
Argues that code review quality improves by treating reviews as conflict to manage not critiques to win and uses conflict‑resolution patterns plus a simple low‑reward / high‑conflict quadrant to decide what to raise. Recommends concrete practices: use a linter in CI to remove bike‑shedding, rotate people and discuss tasks early to create collective ownership, require everyone to review, ask questions not give commands, annotate PRs with targeted questions, say thanks, and practice the “as if” response to lower defensiveness.
AI-written summary · about
chapters (4)
- 0:00Start
- 3:21understand and familiarize yourself with the basic archetypal ways of resolving conflict
- 6:37soliciting the opinion of the author
- 7:50annotate your review
related talks
01h 01mBetter Code Reviews FTW!
56mCode Review — The Art of Growing
46mCode Review, you said?
19mUnlearning Toxic Behaviors in a Code Review Culture
29mCreating a Code Review Culture
37mCode Reviews: Honesty, Kindness, Inspiration: Pick Three
22mBringing A Healthy Code Review Mindset to your team
46mCode Review: We Didn't Come Here to Suffer!
