The Rise and (Potential) Fall of Infrastructure as Code
summary
Clear claim: Infrastructure as Code grew from CFEngine (1993) through Puppet/Chef/Ansible to Terraform (2014), Pulumi (2018), CDK and CloudFormation, but now hits scaling and day‑2 limits and may be at a cliff. Concrete failures include a real Terraform destroy killed production DB incident and a repo with 1,170 hidden lint items that breaks code review. Presenter shows a built alternative—a digital‑twin, multiplayer, one‑to‑one cloud model that claims to reduce drift, enable real‑time collaboration and safer workflows.
AI-written summary · about
chapters (8)
- 0:00Infrastructure as Code intro
- 3:17Origins and evolution of IaC
- 10:19Modern IaC tools and limits
- 17:03Myths and realities of IaC
- 23:27Why IaC fails in practice
- 26:54Future of IaC and generative AI
- 32:38Breaking IaC status quo
- 37:15Closing thoughts & Q&A
related talks
19mInfrastructure as Code: A Must Know Skill for Today's Developers
42mInfrastructure as Code - Lessons learned from Dev to Ops
46mImplementing Infrastructure as Code
54mInfrastructure as code (anti) Patterns
33mScaling Infrastructure as Code
46mThink of your infrastructure as code
01h 02mTools and Techniques for Infrastructure as Code
21mPitfalls of Infrastructure as Code (And how to avoid them!)