The Convergence of Prompt Engineering and DevOps
Prompt engineering entered DevOps not as an experiment but as a pressure valve: teams shipping faster than their tooling could support needed a way to extract precise, repeatable outputs from AI…
Posts tagged terraform.
zopdev writing tagged terraform. Engineering and FinOps notes, post-mortems, and benchmarks.
The Fork That Changed Infrastructure-as-Code Forever
HashiCorp's August 2023 relicense of Terraform from MPL-2.0 to the Business Source License forced every infrastructure team to make a governance decision, not a technical one.
The Hidden Invoice in Your Platform Engineering Budget
Platform engineering teams are paying $180,000 per year in duplicate tooling costs without a line item that names it (ZopDev, "The IDP Tax"). That cost has a name: the IDP tax. It accumulates because…
The Productivity Paradox at the Heart of Most IDPs
Most IDPs ship as friction-reducers and land as a new category of sprint tax. The promise is a self-service portal that abstracts infrastructure complexity. The reality, in production, is a platform…
The Fork Decision: Why Teams Are Reconsidering Terraform
HashiCorp's August 2023 license change from MPL-2.0 to the Business Source License forced every team running Terraform in production to make a governance decision they had not budgeted for. The BSL…
The IDP Bill: $180k/Year in Hidden Platform Toil
Most engineering organizations budget precisely for building an Internal Developer Platform and budget nothing for operating one. The build cost is visible: headcount, tooling licenses, sprint…
Why Your IDP Ships Features Slower After Month 3
Every Internal Developer Platform we have seen hits the same wall: feature shipping slows down at the three-month mark, not because the platform was built wrong, but because the forces that made…
OpenTofu vs Pulumi: Which One Survives a 200-Account Landing Zone
IaC tools built for single-team deployments fail structurally at 200 accounts because the failure modes are architectural, not configurational.
The IDP Adoption Problem: Why Most Platforms Fail
Most IDPs fail because they solve the wrong problem: they build self-service portals instead of standardizing the work developers already do. We measured this in production. Teams spend six months…
The Alert Fatigue Problem in Cloud Policy Management
Traditional cloud alerting creates more work than it prevents because engineers spend 60-90 minutes per day triaging notifications that describe problems without fixing them. The mechanism is…
Self-Service Terraform: 8 Modules That Killed 60% of Our Platform Tickets
Self-Service Terraform: 8 Modules That Killed 60% of Our Platform Tickets Platform teams do not fail because they hire the wrong people. They fail because the right people spend most of their time…
Cloud Configuration Drift: How Silent State Changes Become Expensive Incidents
Configuration drift is the gap between what Terraform declares and what runs in production. AWS Config detects it in 15 minutes. Most teams find it in 72 hours. Here is how to close that gap.
Get the weekly in your inbox.
One post a week. Sundays. No "10 ways to think about cloud" listicles, just the engineering and FinOps notes we'd want to read.