
Error Handling Lessons from Sentry

Python, Go, Rust, TypeScript and AI with Armin Ronacher
Topic 6 of 8
Published Oct 8, 2025 · Clip 47:43–1:05:36 (17:54)
Armin shares lessons from a decade at Sentry: most errors don't carry enough information in production builds, and languages/runtimes neglect error design. He explains why Python's introspectability enabled Sentry's rich error reporting. He compares error patterns across languages—JavaScript errors are frequent but low-signal, C++ game crashes are rare but meaningful—and found TypeScript adoption had no measurable impact on crash rates. He discusses context locals and the trade-offs language designers face between performance and debuggability, including the story of the frame pointer register fight.