Achieving Zero Fronted Crashes in Production
summary
Presents a concrete path to drive production front-end crashes toward roughly zero by combining static analysis, testing, monitoring and process changes. Uses ESLint & TypeScript to catch mistypes, no-floating-promises and hook rules, enforces source maps for readable stacks, and recommends dashboards with dedupe, filtering and alerts. Advocates setting numeric tolerances (example workflow: 100 spikes → 50 → single digits) and running blameless postmortems with the five whys to fix systemic causes.
AI-written summary · about
chapters (9)
- 0:00Start
- 3:52The Bug Acquisition Funnel
- 6:39Code Analysis!
- 6:58Forms of Code Analysis
- 8:43Static Analysis
- 19:33Telemetry
- 20:45Prerequisite Frontend Monitoring Features
- 28:05Virtuous Cycle: Reduction & Prevention
- 35:47Recap
related talks
39mClosing Keynote: Examples of How to Move towards Zero Defects
26mModern Testing Practices in Frontend Applications
33mRoad to Zero Lint Failures: Tackling Code Quality Challenges at Scale
30mHow to push a ReactJS application in production...
28mSome small steps for code, One giant leap for quality
47mEverything I know about writing quality software
34mFantastic Bugs and Where to Find Them
19mThink Prod Up Front: Shifting Left on Production Excellence