Developer-Driven Platforms: Automation and UI Excellence
summary
Core claim: developers cause most incidents because changes slip through from either not understanding vs not testing. Concrete failure: a config change ups production storage with wrong units and CI greenlights it because test environments differ. Concrete fixes: build a UI that knows the schema, move validation earlier into PRs, add targeted automation and guardrails, and log who changed what. A source-available Kubernetes product called batteries included is being built to do this.
AI-written summary · about
chapters (9)
- 0:00intro
- 0:14Introduction and Speaker Background
- 1:51Setting Goals for Developer Platforms
- 3:38Challenges in Balancing Speed and Sustainability
- 4:54Understanding Developer-Induced Incidents
- 8:37Case Study: Production Environment Mistake
- 13:29Building Better Tools and Guardrails
- 17:09Best Practices for UI and Validation
- 20:23Conclusion and Call to Action
related talks
54mDeveloper experience platforms
40mBuilding Developer Platforms, Birds of Feather
26mLessons Learned from 7 years of Running Developer Platforms
11mBuilding Scalable Developer Platforms
31mPanel Discussion: Platform and Developer Productivity - Trends and Challenges
29mImproving Developer Experience
46mWork It Smarter, Dev It Better, Ship It Faster, Test It Stronger
20mDeveloper Experience Is Central to DevOps Success