DevX in the Internet Age: One Step Forward, Two Steps Back
summary
Timeline of tooling from CGI and LAMP spawning per-request processes to enterprise Java lock-in to virtualization and PaaS 1.0 to containers, Docker and kubernetes explains why developer experience oscillates between simpler and more complex. Claim: most teams will stop running kubernetes directly and use clouds like render that hide ops, shrinking SRE headcount. Notes concrete problems: CGI security and performance, lack of private networking in early PaaS, and current kubernetes fatigue plus fragmentation across many vendors.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:40The Five Eras of DevX
- 1:21The Dawn of The World Wide Web
- 3:26The Rise of Enterprise Applications
- 5:41Virtualization and Paas 1.0 Mid-2000s to mid-2010
- 8:12Containers, Kubernetes and 10x Complexity
- 10:19The Importance of Marketing
- 12:08PaaS 2.0: Why It's Different This Time
- 14:06The Decade Ahead
related talks
28mUnleashing Innovation by Unblocking your Developers
05mBare Metal to Containers to K8s: How We Got Here
34mIn the beginning was the server
26mClosing the Developer Experience Gap of K8s Development
15mFireside Chat with AWS and Redmonk | AWS Developer Day 2025
24mFrom Kubernetes to PaaS to Developer Control Planes
32mFrom Kubernetes to PaaS to … Err, What’s Next?
40mBeyond Productivity: Scaling Cloud Dev Environments for Faster Feedback & Sustaina...