Keynote: DX Is the New UX: How Technical Friction Impacts Business Value
summary
Concrete examples of wins and fails: missing discovery (no Stack Overflow or CNCF listing), docs that ignore Helm and kubectl, broken YAML and gated sales processes, and demos that crash in production — one demo uses 16 GB RAM while a realistic baseline is 500 MB with spikes to 2 GB. Winners publish tested CI examples, provide one‑command installs like helm install my-operator, include observability (Prometheus, Jaeger, structured logs), and run load/chaos tests so developers can evaluate fit quickly.
AI-written summary · about
chapters (10)
- 0:00The user experience biryani
- 1:31The consumer decision journey
- 3:42The five principles of DX
- 4:09Mistakes in developer tools
- 4:48Finding and evaluating tools
- 7:29Making onboarding magical
- 7:57Shipping to production
- 9:11Building a thriving community
- 10:18Know your developer
- 11:28Conclusion and takeaways
related talks
16mKeynote: Does Anyone Speak Developer? Methods to Discover, Understand and Improve...
15mKeynote: Creating a Holistic Developer Experience
01h 01mKeynote Presentation Balancing Core Conflicts A DevOps Story
23mKeynote: Enterprise DevOps: Balancing Innovation Velocity with Business Requirements
14mKeynote: Kubernetes is Still Hard (for Developers)
11mKeynote: Like a Magic Eye Illusion: Seeing the Bigger Picture for Cloud-Native S...
53mLet's talk about DX, Baby!
50mKeynote - More than two decades in shell and ops