Corrections and Constructive Criticism
summary
Argues that specific, actionable feedback reduces fear and accelerates skill growth, supported by a workplace that turns reviews into learning so a junior grows into a senior. Recommends concrete tools and habits: use pull requests as storytelling, practice pairing to expose gaps, adopt teacher-style corrections that point at output and offer alternatives, call out power dynamics and phrasing that make criticism hurtful, and prioritize trust over gatekeeping.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:59Fear limits growth
- 6:30Ballet as metaphor
- 9:44Daily feedback types
- 12:36Goals in feedback
- 14:00Ballet lessons for engineering
related talks
32mBetter: Fearless Feedback for Software Teams
35mFrameworks for Feedback
35mFeedback: You don't have to be bad to get better
22mFeedback matters
01h 01mCode Reviews: building better code and stronger teams
42mHow to Lead Open Source Projects and Teams with Better Feedback
19mUnlearning Toxic Behaviors in a Code Review Culture
01h 01mBetter Code Reviews FTW!