Beyond “try harder”: Effective strategies to tackle bugs
summary
Claims concrete results: test suite drops from 30+ minutes to under five (local feedback under one minute), saving about 20 hours per developer per month; deployments move from biweekly to every two days; a critical healthtech service is dark‑launched in parallel with the legacy system using feature flags plus monitoring and observability to catch discrepancies; legacy is replaced incrementally with the strangler fig pattern and trunk‑based flow, CI/CD and test prioritization actually cut batch sizes and make production a low‑risk learning environment.
AI-written summary · about
chapters (7)
- 0:00Failure of 'try harder' approach
- 1:50Overhead and batch sizes create bugs
- 2:54Reset feedback loops under 5 min
- 4:20Beyond checklists with strangler fig
- 5:47Trunk-based development for safer releases
- 7:08Shipping safely with monitoring and flags
- 8:54Faster feedback and controlled delivery
related talks
42mBeyond “Just Try Harder”- Three effective strategies to tackle bugs
36mHow to defuse a bomb Wait, I mean a bug
25mTesting in Production
23mA little less testing, a little more quality
33mTESTING IN PRODUCTION
36mTesting In Production
16mShift Left, Not Off a Cliff: Why Your Testing Strategy Is Breaking Developers
35mTaming a beast