Writing Better Errors

on YouTube ↗32m

" summary

Defines two error classes: user errors (bad input) and server errors (bugs), and recommends concrete fixes: show localized, actionable instructions for user errors, add front-end validation to prevent them, and use clear docs for API consumers. For server errors, log full backtraces and params to Rollbar or similar, notify via a channel, and rely on proper HTTP status codes rather than embedding error codes in 200 responses. For payments, confirm proactively whether a charge succeeded.

AI-written summary · about

" chapters (7)

1. 0:00Start
2. 7:04User Errors
3. 7:52Server Errors
4. 12:48Developer - Input Errors
5. 13:49API User - Input Error
6. 18:16Developer - Server Error
7. 20:22User Server Error

" related talks

• 32mWriting Better ErrorsLaura Eck · Red Dot Ruby Conference 2017
• 06mDX of Error MessagesAtsushi Nakatsugawa · DevRelCon London 2017
• 34mHow to Teach a Service to Report Errors So They're Clear to Users and MachinesA.Lyrchikov · HighLoad++ 2023
• 32mError handling: doing it right!Ruben Bridgewater · JSCamp Barcelona 2019
• 25mAvoiding Disaster: Practical Strategies for Error Handling SlidesHuy Du · RubyConf TH 2023
• 44mA Practical Approach to Error HandlingArno Schödl · ACCU 2022
• 45mThe design of errorFrançois Teychene · Devoxx France 2021
• 31mHow Many Ways to Say I'm Sorry, Error Handling in ReactJesse Martin · React Day Berlin 2019