DevOps or DevX – Lessons We Learned Shifting Left the Wrong Way
summary
Claims that only 52% of new apps reach production and that 83% of developers report burnout drive concrete fixes: adopt platform teams with product mindset, push self‑service and automation so app teams avoid writing YAML for Kubernetes, and apply SRE fundamentals—SLIs, SLOs and error budgets—to trade off cost vs reliability. Examples include treating a 99% SLO as 99% = 403 minutes error budget per 28 days versus a 99.99% target with 99.99% ≈ 4 minutes error budget, which forces automation not human toil.
AI-written summary · about
chapters (10)
- 0:00Start
- 6:37Production is the happiest place on earth
- 13:58Good fences make good neighbours.
- 23:59Reliability is fundamental
- 24:39Service Level Indicators (SLIs), Service Level Objectives (SLOs) and Error Budgets
- 29:16Balancing Change and Reliability
- 32:56Who gets to use the error budget?
- 35:04team sport
- 39:22Absence of Security Incidents is not evidence of good security practices
- 43:12Make the right thing to do, the easy thing to do.
related talks
50mDevOps: Top Lessons Learned on Shifting Left For Accessibility and Other Experts
05mHelp! My DevOps team is stuck!
23mDevOps Is More About Customer Feedback And Quick Learning...
47mDevOps is for Product Engineers, too.
06mLow Growth DevOps
26mTen (Hard-Won) Lessons of the DevOps Transition
47mOvercoming Obstacles to DevOps
31mDevOps for Java Developers (Or Maybe Against Them?!)