Lessons from 25 Years in Infra: What’s Changed, What Hasn’t,...
summary
25 years of infrastructure evolution condenses into concrete lessons: hand-managed servers with ~10GB disks and 64MB RAM give way to CI/CD and config tools like Puppet, Chef, Ansible and build systems such as Jenkins, then cloud on‑demand and Kubernetes-era complexity. Internal developer platforms emerge as costly projects (often millions) that sometimes succeed by delivering a service catalog and dependency graph that speeds outages. Now agentic AI tooling arrives, useful for requests but still needing human guardrails.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:031990s sysadmin
- 5:35Dev vs sysadmin tension
- 8:05DevOps rise
- 10:53Cloud efficiency paradox
- 13:43DevOps failure to platform eng
- 16:13Internal dev portals
- 19:25AI-assisted infra future
- 21:54Key takeaways
related talks
53mFor Want of a Nail: Industry Analyst Lessons Learned on the State of Software Dev...
32mLooking Back At 13 Years Of DevOps
46mThe Rise and (Potential) Fall of Infrastructure as Code
56m14 years of #devops, but what did we really learn
28mUnleashing Innovation by Unblocking your Developers
45mFrom Pets to Cattle: Learning to let go and automate
26mLessons Learned from 7 years of Running Developer Platforms
52mThe Only Constant Is Change: Lessons from a 25 Year SRE Career