How to talk like an Engineer
summary
Claims that poor communication is the root cause in about 95% of project failures and that vocabulary — acronyms, overloaded terms and brand-for-concept swaps like docker vs container or AWS vs cloud — creates most misunderstandings. Practical fixes are explicit: define acronyms first, name internal tools descriptively, stop saying “simple/obvious/easy,” create a permission-to-ask culture, and treat senior engineers as responsible for anticipating edge cases and translating jargon into clear concepts so teams build the right thing.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:42HOW TO TALK LIKE AN ENGINEER
- 2:57FALSE SENSE OF SECURITY
- 6:16WHAT ARE THE CONSEQUENCES?
- 8:06LACK OF ADOPTION
- 8:19ABANDON THE PRODUCT
- 8:41BUILDING THE WRONG THING
- 9:44Vocabulary is a huge component to learning any new language and programming languages are no exception.
- 11:40THERE ARE A LOT OF TERMS TO KNOW
- 12:06NEWBIE EXCLUSIVE PROBLEM
- 12:35NEW TO THE TECH? NEW TO THE TEAM?
- 15:36HOW DO YOU SOLVE THE PROBLEM OF WORDS YOU DON'T KNOW?
- 16:02ACRONYMS
- 18:08OVERLOADED TERMS
- 18:32PRODUCT NAMES AS CONCEPT
- 21:48NEW CORE CONCEPTS
- 25:20YOU'RE AN EXPERT
- 27:40ANTICIPATE CHALLENGES
related talks
15mIt Works on My Machine: Why Engineers Are Misunderstood (and What They Can Do About It)
42mWhen Jargon Becomes Gibberish
23mCommunication is just as important as Code
45mHow to Communicate Technical Ideas to Non Technical Audiences
45mHow to Communicate Technical Ideas to Non Technical Audiences
27mHow 'Up & Running' Culture is...
34mThe Art and Science of Communication
47mImprove your code by improving your communication