The Minds Behind Infrastructure as Code – 7 People Redefining Software
Seven pioneers helped turn servers, networks, cloud resources, and configuration into versioned, testable, declarative software artifacts.
TL;DR
Seven pioneers helped turn servers, networks, cloud resources, and configuration into versioned, testable, declarative software artifacts. [1][2]
Why you should read it anyway
Infrastructure as code changes infrastructure from a collection of undocumented manual actions into a reproducible system definition. Once environments are described in source control, teams can review changes, recreate systems, test assumptions, automate delivery, and understand how infrastructure evolved.
Imagine where Infrastructure as Code would be without them
Without this lineage, cloud APIs would still make infrastructure programmable, but the convergence models of CFEngine and Puppet, Chef’s programmable configuration, Terraform’s provider graph, and IaC’s software-engineering discipline would have coalesced more slowly.
Time Estimate of how many years we would be hindered without them for human progress
Editorial counterfactual estimate: 4–8 years. This is not a measured historical fact. It is an editorial estimate of how much slower the field might have matured without this cluster of people, institutions, practices, and tools.
The 7 people behind Infrastructure as Code
1. Mark Burgess
Why they matter: created CFEngine in the 1990s and pioneered policy-based, convergent configuration management. His work anticipated infrastructure as code by treating system configuration as declarative desired state that software could continuously enforce.[1]
2. Adam Jacob
Why they matter: created Chef and helped bring infrastructure automation into a programmer-oriented model where configuration could be expressed as code, versioned, tested, reused, and integrated with software-delivery workflows.[2]
3. Luke Kanies
Why they matter: created Puppet, which popularized declarative configuration management through resources, manifests, and convergence toward desired state. Puppet helped make configuration code a standard layer in large Unix and cloud environments.[3]
4. Mitchell Hashimoto
Why they matter: co-created Terraform and designed a cloud-agnostic workflow for describing provisioned infrastructure declaratively. Terraform extended infrastructure as code beyond machine configuration toward APIs for networks, cloud resources, managed services, and entire environments.[4]
5. Armon Dadgar
Why they matter: co-founded HashiCorp and co-created Terraform with Hashimoto. He helped shape its declarative graph model, provider ecosystem, and workflow for planning and applying infrastructure changes safely across heterogeneous platforms.[5]
6. Kief Morris
Why they matter: systematized infrastructure-as-code principles in writing and practice, emphasizing reproducibility, version control, testing, continuous delivery, and dynamic infrastructure. His work helped distinguish IaC as an engineering discipline rather than simply writing automation scripts.[1]
7. Yevgeniy Brikman
Why they matter: helped popularize reusable, testable infrastructure modules and practical Terraform engineering through books and open-source work. His guidance connected infrastructure code with software-engineering practices such as automated testing, modularity, and release discipline.[2]
How they each differ from one another
Burgess pioneered convergent policy; Kanies and Jacob industrialized configuration management through Puppet and Chef; Hashimoto and Dadgar expanded IaC into cloud provisioning with Terraform; Morris articulated the discipline; Brikman emphasized modular, tested infrastructure code.
Final Take
Infrastructure as code erased a false boundary: infrastructure is part of the software system. If an environment matters to production behavior, its definition belongs in the same engineering conversation as application code.
Works Cited
- 01CFEngine — Infrastructure as Code lineage cfengine.com
- 02
- 03HashiCorp — The Story of Terraform hashicorp.com
- 04Terraform — Documentation developer.hashicorp.com
- 05Martin Fowler — Infrastructure as Code martinfowler.com
CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.
Submit a research lead