Comparative Error Handling...
summary
Compares concrete failures and fixes across ecosystems: JavaScript shows unexpected token < in JSON from fetch responses and silent module-load failures caused by syntax errors, Ruby surfaces undefined method posts for NilClass and no implicit conversion of String into Integer from mistaken array indexing, Heroku logs can literally say we need a better air and be useless. Argues error handling is predictably broken, cites ~135k JS “better error” issues vs ~44k Ruby, and recommends autocorrect tools (RuboCop/ESLint), intent-aware diagnostics, and linking docs in errors.
AI-written summary · about
chapters (21)
- 0:00Intro
- 1:45Technical Hurdles
- 2:36Error Handling
- 3:36Error Messages
- 4:02Failure
- 4:23This is our fault
- 6:14Uncaught Error
- 8:40Error Logs
- 9:56Hypothesis
- 11:09Installation Error
- 11:45No Method Error
- 14:02No Implicit Conversion Error
- 15:33Predictable Error Handling
- 15:58Error Messages for Developers
- 18:53Syntax Error
- 20:34Lazy
- 21:23Better Error
- 23:25Fixing Error Handling
- 26:13Community Support Resources
- 28:48Writing for Users
- 30:44Building Trust
related talks
30mHuman Errors
40mManeuvering Errors within the Bowels of JavaScript
36mDon’t be afraid of the scary red error messages;...
30mRuby on Fails: effective error handling with...
39mSteal This Talk: The Best Features Ruby Doesn't Have (Yet)
33mRuby and Go
37mException Handling Designing Robust Software
35mThe worst Ruby codes I've seen in my life