Infrastructure as Code - Lessons learned from Dev to Ops
summary
Argues that applying application-development practices accelerates Infrastructure as Code maturity and shows concrete tooling and workflows: CloudFormation and Terraform, Ansible, kitchen‑terraform with InSpec, cf‑nag/terraf lint and CI pipelines. Demonstrates a layered CloudFormation build (networking unchanged after nine months, app stack changing daily) and automated sandboxes for apply‑then‑test. Claims unit testing and peer review cut errors but adoption is low (about three audience members admit testing). Recommends parameterization, export/import of values, and explicit dependency modeling.
AI-written summary · about
chapters (26)
- 0:00Intro
- 0:30DevOps consultancy
- 1:44Im a developer
- 3:43Agile themes
- 4:23Code reuse
- 5:30Thirdparty libraries
- 8:39Unit testing
- 11:21Unit tests
- 12:27Inspect tests
- 12:55Inspect examples
- 14:00Static code analysis
- 14:36Syntax checking
- 16:28Peer review
- 17:38Manual testing
- 18:18Invest Principle
- 18:54Given When
- 20:06Team Appetite
- 21:15Technical Excellence
- 23:47Application Structure
- 27:09Transformation
- 27:54Layered example
- 28:53Explicit dependency management
- 30:03Whiteboard
- 30:54Product Owner
- 32:37Coneshaped Engineers
- 34:40Crossfunctional Teams
related talks
46mImplementing Infrastructure as Code
19mInfrastructure as Code: A Must Know Skill for Today's Developers
46mThink of your infrastructure as code
54mInfrastructure as code (anti) Patterns
01h 02mTools and Techniques for Infrastructure as Code
46mThe Rise and (Potential) Fall of Infrastructure as Code
32mCode Quality and Infrastructure as Code
28mInfrastructure as Code in the Real World