The Arcane Art of Error Handling
summary
A pragmatic set of patterns for large Rails apps that actually shipped at Procore and scaled to a two million line codebase with ~90–100 engineers and 4–5 deploys a day involves building an ErrorHandler class, custom exception hierarchies, and metadata and severity for Bugsnag to filter noise and route alerts, using user_message instead of Exception#message for i18n, wrapping third party timeouts to preserve causes, three behaviors of errors fail fast, rescue and continue, or rescue and translate to status codes, and adding ids for log correlation
AI-written summary · about
chapters (5)
related talks
30mRuby on Fails: effective error handling with...
37mException Handling Designing Robust Software
29mResolve Errors Straight from the Error Pages
31mCoding for Failure
38mThe Design of Error
28mHow to get to zero unhandled exceptions in production
41mExceptional Ruby
32mExpect the Unexpected: How to Deal with Errors in Large Web Applications