Writing Better Errors

on YouTube ↗32m

" summary

Errors target different audiences and should be split: log full backtrace and params to a service like Rollbar or Airbrake so developers get actionable diagnostics, return use matching HTTP status codes and a clear response body for API consumers, and show localized, concise messages with exact next steps and front‑end validation to app users. Differentiate transient failures (suggest retry) from data or payment issues (offer support or promise proactive follow‑up) and surface frequency metrics to fix UX hotspots.

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 · RedDotRubyConf 2017
• 06mDX of Error MessagesAtsushi Nakatsugawa · DevRelCon London 2017
• 32mError handling: doing it right!Ruben Bridgewater · JSCamp Barcelona 2019
• 22mYes, Your Error Messages Can Be Beautiful And Developers Can Love ThemYoz Grahame · DevRelCon Earth 2020
• 31mHow Many Ways to Say I'm Sorry, Error Handling in ReactJesse Martin · React Day Berlin 2019
• 23mDeciphering Alerts – Why is it so hard to make senseLena Nyström · HUSTEF 2024
• 45mThe design of errorFrançois Teychene · Devoxx France 2021
• 34mHow to Teach a Service to Report Errors So They're Clear to Users and MachinesA.Lyrchikov · HighLoad++ 2023