Skip to content

Latest commit

 

History

7 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Infrastructure as Documentation: Designing IaC That Explains Itself

Status: Active 🗣️Talk 🟢 Intermediate

Short Abstract

Infrastructure as Documentation treats IaC as executable contracts. Learn how to surface intent through Terraform structure, naming, and outputs, apply patterns that translate across IaC tools, and refactor messy modules in a live teardown. Leave with designs that improve auditability and reduce cognitive load.

Abstract

Infrastructure as Documentation reframes IaC from “infrastructure scripts” into executable contracts that make intent, boundaries, and assumptions unmistakably clear. Most IaC rots because the why behind the code is invisible; teams inherit modules they don’t understand, reviews become superficial, and governance drifts into side documents no one maintains. This session shows how to design Terraform so that the code is self-documenting, reviewable, and resilient to turnover.

Attendees learn a contract‑first approach that surfaces intent directly through module structure, naming, variables, and outputs. They get a portable pattern library that applies across IaC tools: Terraform is the teaching medium, but the principles translate cleanly to ARM/Bicep, CloudFormation, Pulumi, CDK, and others. A live teardown of a messy Terraform module demonstrates how to uncover hidden intent, refactor for clarity, and align infrastructure with governance without adding bureaucracy.

By the end, participants can design IaC that scales, withstands team changes, improves auditability, and reduces cognitive load for every engineer who touches it.

Type

  • 45/60/75-minute session

Tags

Infrastrcuture as Code Platform Engineering DevOps Terraform

Learning Objectives

  • Design self-documenting IaC: Create Terraform modules that explicitly communicate intent, boundaries, and assumptions through structure, naming, variables, and outputs.
  • Uncover and refactor hidden intent: Diagnose where IaC obscures the "why," then systematically refactor messy modules to improve clarity, auditability, and team comprehension.
  • Apply portable contract-first patterns: Use a cross-tool pattern library that scales across Terraform, ARM/Bicep, CloudFormation, Pulumi, and CDK to build IaC that survives turnover and reduces cognitive load.

Presentations

Event Location Date Time Room Downloads
DevOpsCon New York 2026 New York, NY 2026-09-29 10:30 EDT TBA Slides |Handout |Demos

Email chadgreen@chadgreen.com to have Chad present this session at your event.

About

Infrastructure as Documentation treats IaC as executable contracts. Learn how to surface intent through Terraform structure, naming, and outputs, apply patterns that translate across IaC tools, and refactor messy modules in a live teardown. Leave with designs that improve auditability and reduce cognitive load.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors