The Mistake of Assuming an Error
summary
Argues that ambiguous error messages and vague documentation (e.g., “undefined is not a function”, “expected comma”) break developer trust and workflow. Describes rewriting and redesigning the Origami registry: replacing obsolete instructions with an explicit install command and a clear purpose description, and shows via a cake anecdote that adding context and elaboration prevents hours of needless debugging.
AI-written summary · about
chapters (10)
- 0:00Start
- 5:02For a piece of cake, please leave comments
- 6:29error messages
- 9:18TypeError: undefined is not a function
- 10:16Uncaught Error [object object]
- 17:30clarity in elaboration
- 20:44we understand the world through words
- 21:33Everyone knows 'Real programmers...
- 23:45elaborate without judging, offer space for suggestions
- 24:01assumptions
related talks
26mPractice Makes Perfect: Write Accessible Documentation
51mGetting the Most Out of Your Shift Left Regardless of Your Program Maturity
40mCognitive Ergonomics in Technical Writing - Lessons from the Field
49mEmbedded cultural assumptions: how to annoy and insult your users in one easy step
49mUsability for Developers
47mHow complex software impacts your cognitive abilities
50mThe Crisps and Pickle Story: What's Really Behind Infamous, Historic UI Failures?
53mThe Folly of Chasing Demographics