Communication is just as important as Code
summary
Argues that code quality fails when communication artifacts fail and treats tests, commit messages, naming and error text as first‑class deliverables; defines legacy as code without tests or communication artifacts; recommends adding the team’s spoken language to the tech stack and using empathy‑driven practices like detailed timesheets and clearer error messages. Proposes concrete patterns: an inception level to signal interruption cost, use yes and instead of “well actually,” and apply radical candor (care personally, challenge directly) for feedback.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:07Scott Ford
- 4:09Add another Language to My Tech Stack
- 5:20Poor Communication Creates Poor Systems
- 7:12Degree Envy
- 8:14What Is Communication
- 14:41Why Should We Care about Communication
- 16:43Patterns and Frameworks
- 18:19Shattering Glass
- 19:12How To Give and Receive Feedback without Being Mean
- 19:38Radical Candor
- 21:39Final Words
