Leading with empathy: Turning good developers into great engineers
summary
Defines empathy as "stepping into someone else’s shoes" and shows concrete failures and fixes: sloppy code docs and copy‑pasted PHP docs, a non‑empathetic standup reply versus a concise yes/no, and the Mars Climate Orbiter unit mixup that costs about $500M. Recommends practical fixes: use tooling to surface conflicts and feedback, publish a manager‑on‑a‑page, bake empathy into a GREAT expectations framework, force face‑to‑face collaboration and give direct feedback to change team behaviour.
AI-written summary · about
chapters (9)
- 0:00Introduction and welcome
- 0:47About the speaker and empathy
- 2:13Why empathy matters in engineering
- 3:40Communication pitfalls in tech
- 5:26Empathy in code and documentation
- 7:36Empathy for engineering leaders
- 9:42Grown vs new CTO challenges
- 11:48Practicing empathy in teams
- 12:52Closing and Q&A
related talks
19mEngineering with Empathy
28mOne weird trick to becoming a better software developer
11mWhy Empathy Matters in Open Source Software Development
44mPractical Empathy: Unlock the Super Power
26mThe Other Side of Empathy
41mThe Principles of Empathetic Programming.
57mCompassion ++: Soft Skills for Hard Problems
18mLeading with Empathy