The Exceptions We Don't Catch in Technical Conversations
summary
Argues that most failures are sociological not technical and demonstrates concrete practices: replace global judgments with I find this code confusing, name the problem you own, and invite curiosity instead of triggering a defensiveness exception. Cites books (Peopleware, Nonviolent Communication, David Burns) and reports a striking empirical result: about one third of the time the critic is actually wrong. Implements these tools as a conversational refactor and shows they reduce escalation and often turn criticism into explanation rather than argument.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:53Hidden evaluations in feedback
- 7:46Using I statements
- 15:03Defensiveness antipattern
- 20:00Complementary strengths
- 23:09Reframing conversations
- 24:56Communication frameworks
- 25:38Q&A on AI code
- 28:46De-escalating conflicts
- 30:31Mistakes and cultural differences
- 32:56I statements in code reviews
- 35:44Closing remarks
related talks
57mDebugging Difficult Conversations - Or "How not to chicken out"
37mFixing the mistakes we -all- make as developers, leaders and teams
47mCrucial Conversations: tools for handling difficult conversations
49mBugs in Collaboration: "Learning from Incidents" Edition
34mYou're a problem solver
23mCommunication is just as important as Code
43mHow to deal with the social side of computing life
01h 04mAre You a Screwdriver?