Should My Team Really Need to Know Terraform?
summary
Grainger builds a self‑service delivery platform that uses Terraform but argues most application teams shouldn't need to be Terraform experts; platform exposes accelerators and starter kits plus an engineering portal and libraries with versioned changelogs. Provisioning drops from weeks or months to hours or a day for common cases, while guardrails (enforced encryption at rest, tests, ownership) handle non‑negotiables; 80/20 usage splits guide when teams must learn the tool versus consume abstractions.
AI-written summary · about
chapters (6)
- 0:00Introduction and team background
- 4:12Early struggles with Terraform
- 9:28Security requirement and inefficiencies
- 10:55Platform team improvements
- 13:45Platform principles and trade-offs
- 20:47Final thoughts and Q&A
related talks
32mUnlocking high-velocity engineering through automation, self-service, and Terraform
24mTerraform Best Practices
28mSupport and Tools to Help You Accelerate Toward DevOps
30mMastering Terraform: A deep dive into essential workflows
18mThe Path to Modern Infrastructure Automation [Abridged]
19mHow We Built a DevOps Dojo to Upskill Our Organization in Terraform
13mNavigating the infrastructure skills gap for DevOps teams
28mYour Terraform setup is the foundation for an IDP — extend it to empower developers