Infrastructure

The drift-state extension makes zero AWS API calls. It reads data that other models already produced, diffs it against a stored baseline, and writes the result as typed versioned state. The “drift detector” is a composition function over existing observations. This matters because drift detection is usually sold as a feature of a specific tool. CloudFormation has drift detection. Terraform has plan. AWS Config has compliance evaluations. Each one instruments its own slice and reports on what it manages. Nothing composes across them. ...

The sandbox that teaches you swamp is itself managed by swamp. A system whose primitives are general enough to manage cloud infrastructure, editorial workflows, and security scans can also manage the disposable learning environment that introduces all of those patterns. The problem with demos Most developer education follows a pattern: here is a tool, here is a contrived example, here is a README explaining how the contrived example relates to your real work. The gap between the tutorial and production is where most people give up. ...

Every Terraform file you ever wrote was a note to a blind tool. You looked at your infrastructure, decided what it should be, wrote that decision into HCL, and handed it to a program that could not see for itself. The declaration was your observation, pre-computed and frozen into a file. The same was true for Chef recipes, Puppet manifests, and CFEngine promises. You observed the system. You wrote down what you saw and what you wanted. You gave that note to an agent that could parse files but could not look around. ...