Faking Coherence for Engineers
summary
Release engineering at Chef includes CI, packaging and publishing tools, and the core claim is that coherence acts like invisible infrastructure whose failures create measurable friction. Fixing it fully is impossible, so practical tactics matter: finish your sentences, limit repetition, use canned responses and docs, deploy heuristics, and corral meetings with sticky notes. A concrete habit is boiling a complex ask down to a single sticky note; another is sending a detailed diagnostic email once and reusing it as an artifact.
AI-written summary · about
chapters (31)
- 0:00Introduction
- 1:08What is coherent
- 4:15Why do I care
- 4:55Invisible Infrastructure
- 7:27How does lack of coherence create friction
- 8:04Why does coherence matter
- 11:12Why not just fix it
- 11:22I dont think you can
- 11:40Nobodys perfect
- 12:08Perception of coherence
- 13:49Incoherence
- 14:58Craft field
- 16:53What can we do
- 17:19Put a decent API in front of your brain
- 17:54Coherence is relational
- 20:00Finish your sentences
- 21:02Limit repetition
- 22:04Hand responses
- 26:45Corral conversations
- 27:14Sticky notes
- 29:29Specific responses
- 31:15Reset the conversation
- 31:54Stop and turn around
- 32:17Strategic questions
- 32:41Audience questions
- 33:20Circle of commitment model
- 34:41Different conversation
- 36:03Historical conversations
- 36:55Conversational base
- 38:50Strategy
- 40:35Blessing
related talks
01h 01mFixing the Ultimate Legacy System: You
31mStorytelling for Engineers
48mHow to Build and Maintain Engineering Teams Focused on Product through Culture and Values
30mHow to talk like an Engineer
22mHow to be an inefficient developer?
04m"Fail.lure"
52mSecrets of a Strong Engineering Culture
46mCracking the cadence of your software engineering 1:1s