// Topic
Infrastructure As Code
Definition
Infrastructure As Code coverage in this archive spans 3 posts from Jun 2016 to Nov 2022 and focuses on reliability, delivery speed, and cost discipline as one system, not three separate concerns. The strongest adjacent threads are terraform, devops, and cloud. Recurring title motifs include infrastructure, scale, terraform, and code.
What the archive argues
- Most posts prioritize predictable operations over feature breadth or stack novelty.
- The consistent theme from 2016 to 2022 is disciplined execution over hype cycles.
- This topic repeatedly intersects with terraform, devops, and cloud, so design choices here rarely stand alone.
Execution checklist
- Set SLOs first, then choose tooling that keeps deploy, observability, and rollback simple.
- Start with the newest post to calibrate current constraints, then backtrack to older entries for first principles.
- When boundary questions appear, cross-read terraform and devops before committing implementation details.
Common failure modes
- Adding platform layers faster than the team can operate and debug them.
- Chasing throughput gains without proving they improve end-user reliability.
- Applying guidance from 2016 to 2022 without revisiting assumptions as context changed.
Suggested reading path
- Start here (current state): Infrastructure as Code Patterns That Actually Scale
- Then read (operating middle): Terraform at Scale: What Changed Since 2019
- Finish with (foundational context): Why I Moved Our Infrastructure to Terraform
Related posts
- Infrastructure as Code Patterns That Actually Scale
- Terraform at Scale: What Changed Since 2019
- Why I Moved Our Infrastructure to Terraform
References
3 posts
- Infrastructure as Code Patterns That Actually Scale
Practical Terraform patterns for teams that have outgrown the tutorial stage: module design, state management, environment promotion, and policy enforcement.
Terraform at Scale: What Changed Since 2019
Two years ago I wrote about Terraform patterns for growing teams. Here's what held up, what broke, and what I do differently now.
Why I Moved Our Infrastructure to Terraform
We moved from console-driven, script-heavy infrastructure to Terraform so changes are reviewed, reproducible, and recoverable from code.