Kind Engineering: How To Engineer Kindness
summary
Covers concrete practices: code review tone tactics like ask open-ended questions, call out nitpicks and automate formatting (linting) when more than five is a lot of nitpicks, shift to synchronous chat when threads get long, and debrief PR authors rather than public piling. Gives feedback process: what went well what went badly what can I do differently, wait 10–15 minutes before reacting to criticism, codify kindness via a culture deck, and cites Give and Take and Radical Candor for theory.
AI-written summary · about
chapters (9)
- 0:00Start
- 5:14Code Reviews
- 11:59Honesty
- 12:19Being at work
- 17:41Psychological Safety
- 19:23Encourage Feedback
- 22:24Be Inclusive
- 25:07No Blame
- 27:07Turn Failure Into Learning
related talks
40mEngineering Kindness
19mEngineering with Empathy
38mNorDevCon2020 - Day 2 - Part 3 - Jon Skeet
32mCaring For Your Fellow Developers
20mPrompt Engineering for People: What AI Can Teach Us About Effective Communication
13mLeading with empathy: Turning good developers into great engineers
29mThe art of humanizing Pull Requests (PR’s)
26mThe Other Side of Empathy