The Principles of Empathetic Programming.
summary
Argues that empathy measurably reduces technical friction and bugs, with concrete tactics: check prior knowledge, document why (link bug tickets), prefer incremental rewrites, rotate maintenance work, and build psychological safety — citing Google’s team study and Elizabeth Newton’s experiment (3 in 120 got it, tappers guessed 50% confidence). Gives real product context: a house-built editor and engine across platforms and a shipped game Erica (Sony 2019) and cites Apollo 11 software hiccup as a cautionary example.
AI-written summary · about
chapters (16)
- 0:00Empathetic programming intro
- 3:43Understanding others is hard
- 8:59Reading others' code
- 12:50Improving existing code
- 15:57Maintenance vs innovation
- 20:14Reasonableness and fallibility
- 23:03Psychological safety power
- 25:11Kindness with honesty
- 26:37Key takeaways
- 29:45Q&A on conduct
- 31:31Reflecting on past code
- 32:33Importance of positive feedback
- 34:16Cultural kindness differences
- 37:29Safety strategies
- 38:53Code history tracking
- 40:57Closing remarks
related talks
32mEmpathy Maketh an Engineer
13mLeading with empathy: Turning good developers into great engineers
11mWhy Empathy Matters in Open Source Software Development
44mPractical Empathy: Unlock the Super Power
19mEngineering with Empathy
28mOne weird trick to becoming a better software developer
29mDeveloping With Empathy
01h 04mEmpathy as a Technical Skill