Code review friction
Does your team agree on what code review is actually for?
👋 Hey, it’s Stephane. I share lessons, and stories from my journey to help you lead with confidence as an Engineering Manager. To accelerate your growth see: AI Interview Coach | 50 Notion Templates | The EM’s Field Guide | CodeCrafters | Get Hired as an EM | 1:1 Coaching
Paid subscribers get 50 Notion Templates, The EM’s Field Guide, and access to the complete archive. Subscribe now.
Somewhere on your team right now, an engineer is spending five minutes rewriting a two-sentence PR comment. They’re softening it. Adding a “maybe” here, a question mark there. Wondering if “consider” sounds too commanding or too passive. They’ll eventually settle on something that sounds polite but vague enough that the author won’t know whether to act on it.
Meanwhile, another engineer on your team is writing “just do X” and hitting submit without a second thought. Not out of malice - they just want to get through open PRs before standup.
Both of these people think the other one is doing it wrong. And you…




