Panic Driven Development
summary
A junior engineer breaks the user creation form during a Monday deployment, finds and ships a fix in 15 minutes amid panicked manual debugging, and learns that would have been avoided with automatic quality gates. The concrete claim: CI tests and quality gates act as a safety net that reduce risk, prevent frantic hotfixes, and let less experienced engineers experiment and contribute without fear.
AI-written summary · about
related talks
35mWhy Software Engineers Should Make Quality a Priority
38mBuilding a high quality product
21mDeveloper-Driven Platforms: Automation and UI Excellence
15mQuality Engineering Journey from Shift Left to Shift Right and Beyond
21mDevelopers vs Quality Assurance
26mIs Your Gatekeeper Locking Out Quality?
43mDeveloper Driven Security In High-Growth Environments
12mConvergent Quality Engineering