What is Developer Empathy?
summary
Claims specific steps that change outcomes: psychological safety raises retention, trust and productivity; implement a six-week anonymous survey with explicit DEI questions to measure voice and interruptions; require tests and screencast on PRs so reviewers see behavior and speed delivery; set DTR working agreements, regular pairing, and public praise plus private, specific feedback. These tools produce measurable behavioral change rather than vague encouragement.
AI-written summary · about
chapters (22)
- 0:00Start
- 0:20Humility
- 3:50Identity Markers of Power and Extreme Privilege
- 6:13Empathy Fuels Connection and Sympathy Drives Disconnection
- 8:57Empathy Is Not a Hardwired Trait
- 12:08Acknowledge My Own Power
- 13:07State Expectations
- 19:56What Does Support Look like for You
- 20:46What Can Engineering Leaders Do
- 21:14Implicit Bias
- 23:09Establish Empathetic Team Norms
- 23:59Call Out Great Work in Public
- 24:40Critical Feedback
- 28:52What Could You Do To Create a More Safe and Inclusive Culture in this Team but some Personal Responsibility
- 29:48Rethinking Meetings
- 35:45Define Your Working Style
- 39:38Active Listening
- 45:03Building in Joy
- 50:08Asking for Help
- 50:23Psychological Safety
- 54:43Pairing
- 57:15Challenge Our Own Assumptions
related talks
02h 23mDeveloper First: A New Leadership Mindset
30mDeveloper First – A New Leadership Mindset
13mLeading with empathy: Turning good developers into great engineers
22mKeynote Session: Developer Empathy - The Overlooked Tool to Elevate Open Source Communities
28mOne weird trick to becoming a better software developer
13mEngineering Empathy...
44mEmpathetic Communication for Developers
45mHelping Developers to Help Each Other