General-purpose IaC earns its complexity where application engineers own infrastructure and benefit from typed components and unit tests. It disappoints when the pitch was freedom: the engine still builds a graph, still keeps state, and still forbids most of the clever runtime logic people expect to write.
← Infrastructure as Code & Configuration / 25
hardNewStripeDatabricksSnowflake
A team wants to ditch HCL for Pulumi because they prefer TypeScript. Where do you agree, and where do you refuse?
General-purpose IaC earns its complexity where application engineers own infrastructure and benefit from typed components and unit tests. It disappoints when the pitch was freedom: the engine still builds a graph, still keeps state, and still forbids most of the clever runtime logic people expect to write.
Updated Sep 2026 · Grounded in researched DevOps, SRE and platform engineering interview loops, written to a senior-engineer editorial bar, and never padded to hit a word count.
20 answers per topic instead of 10, and your progress kept · no cardor unlock all 390 remaining answers · ₹2,000 / $25
UP NEXT ON YOUR JOURNEY
Next in this trackSome teams moved to OpenTofu after the license change. What actually differs, and how do you stay portable?Next in this trackA resource was deleted by hand in production and every plan now wants to recreate it. Walk me through safe state surgery.Next in this trackApp teams promote builds from dev to staging to production. How should promotion work for infrastructure changes?
DISCUSSION · 0
Nothing here yet. Say how you would answer it.