What, What? - When We Think We Understand
summary
Three concrete misunderstandings are described with plain examples: a lightning charger mistaken for weather, reflections confused with meditation instead of runtime inspection, and shipping containers imagined as trucks not Linux images. The claim is that shared words with domain-specific meanings regularly cause friction and escalate conflicts. The fix offered is specific and immediate: pause, ask a clarifying question, and do a quick check‑in to align assumptions before proceeding.
AI-written summary · about
chapters (9)
- 0:00Intro: The Wait, What? Moment
- 0:30Miscommunication Over “Lightning”
- 1:20Reflections: Code vs Meditation
- 1:50Containers Confusion
- 2:20Language Differences in Tech
- 2:50Why Shared Understanding Matters
- 3:20Misunderstanding in Developer Teams
- 3:50Simple Fixes: Ask, Clarify, Connect
- 4:00Closing Thoughts on Communication
related talks
30mHow to talk like an Engineer
32mI Read It But Don’t Get It, or How to Tackle Technical Texts
30mThe Curse of Knowledge
31mDangerous Minds: How we're getting developer education wrong
26mHow to Think
40mStructures of Thinking: Mental Models, Levels of Reasoning (...)
26mTake a step back
41mYour Customers Aren't Stupid and Your Coworkers Are Not Incompetent