Caring For Your Fellow Developers
summary
Caring is an action, not a feeling: concrete tactics include rewriting blunt review comments into reasoned critiques, scheduling flexible one‑on‑ones (try walking meetings), closing the shop sometimes to learn personal context, and leaving praise as often as critiques. Code‑review rules are practical — ask questions often, explain frequently, never decree — and psychological safety matters: Google’s Project Aristotle studies over a hundred teams and shows safety predicts effectiveness. Be available, notice when someone looks off, and make small supportive moves.
AI-written summary · about
chapters (9)
- 0:00Start
- 6:14Code Reviews
- 12:49Make Opportunities for Praise
- 15:11Psychological Safety
- 15:27Psychological Safety
- 20:43Day-to-Day Activities
- 21:01Close the Shop
- 27:17Be Available and Be Open
- 30:13Steve Jobs
related talks
46mKind Engineering: How To Engineer Kindness
09mThe Art of Giving and Receiving Code Reviews Gracefully
01h 01mThe Care and Feeding of Software Engineers
18mHow To Review Someone's Code While Not Being A Jerk!
32mThe Care and Feeding of Software Engineers
01h 01mCode Reviews: building better code and stronger teams
56mThe Care and Feeding of Software Engineers
34mCompassionate Coding: Showing Care Between the Keyboard and the Chair