Communication: What are you Thinking About?
summary
Argues that most software failures come from miscommunication and gives concrete fixes: attach screenshots to issues because images travel 60,000 times faster through understanding; keep subject lines short; after three or four back-and-forths close and write a new ticket and reference the new number; stop adding people to late projects (Brooks law) and beware shared‑component shortcuts that force checking nine places; reproduce errors by copying and manipulating URLs for exploratory testing; cite Intel 1994 CPU bug, healthcare.gov two‑week testing, and Apple’s eight‑step rollback as costs of shortcuts.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:44Why did it fail
- 1:04Lack of communication
- 2:02Brooks Law
- 3:14Communication
- 3:34Visual aids
- 7:19Shortcuts lead to long delays
- 8:43Healthcaregov
- 9:20Apple
- 9:55The Fix
- 10:34Fail
- 10:47Testing
- 11:02Failure
- 11:19Failure is awesome
- 12:14Failure without fear
- 14:43Experiment
- 16:48Product
- 17:07Mazda
- 17:55iPhone 6 Plus
- 19:25Criticism
- 22:11Conclusion
related talks
49mKeynote: Debug your thinking
23mCommunication is just as important as Code
55mImprove your thinking, improve your software
46mIt’s Never a Technology Problem: Using Experience to Solve the Problem
06mLightning Talk: Undefined Behavior - Toolkit to Improve Communication With Clients
55mBlame. Language. Sharing: Three Tips for...
23mHow To Win Designers And Influence Developers
38mFallacies of Software Development