Infrastructure as Code
Terraform, OpenTofu, CloudFormation and the principles behind reproducible infrastructure.
THE ANYTHING AS CODE SCHOOL
If it can be defined, it can probably be code.
CloudSchool.dev is a practical learning space for engineers who want to go beyond Infrastructure as Code — and discover what happens when we start treating everything as code.
// the big idea
Code isn't just how we build software anymore.
It's becoming how we describe, validate, reproduce, govern and operate the systems around it.
CloudSchool.dev will explore the patterns, tools and thinking behind this shift — from familiar DevOps practices to surprising applications you may not have considered.
idea
→ declarative
declarative
→ versioned
versioned
→ reviewable
reviewable
→ automatable
automatable
→ repeatable
repeatable
→ scalable
// curriculum.loading()
The classics. Then the interesting stuff.
Expect practical guides, patterns, examples and experiments across the growing universe of “as code”.
Security as Code
Encode security controls, scanning, guardrails and security policies into the delivery lifecycle.
Policy as Code
Turn organizational rules into executable, testable and continuously enforced policies.
Documentation as Code
Versioned knowledge, architecture decisions, runbooks and documentation that evolve with the system.
Everything as Code
Explore the common patterns hiding behind all these disciplines — desired state, automation and feedback.
GitOps & Automation
Git as the system of record. Pull requests as change control. Automation as the execution layer.
// things you might not expect
What else could become code?
The fun starts when you stop asking “what tool should I use?” and start asking “what can I describe precisely enough to automate?”
01
Architecture as Code
Define system architecture as machine-readable models, validate architectural rules and generate diagrams from reality.
02
Compliance as Code
Express regulatory and internal controls as automated, continuously tested rules instead of periodic spreadsheets.
03
FinOps as Code
Encode budgets, tagging requirements, cost thresholds and cloud-spend guardrails into automated workflows.
04
Observability as Code
Define dashboards, alerts, SLOs and telemetry pipelines alongside the systems they monitor.
05
Disaster Recovery as Code
Encode recovery procedures, dependencies, validation tests and recovery environments instead of relying on binders.
06
Developer Experience as Code
Define golden paths, developer environments, templates and team workflows as reusable building blocks.
07
Knowledge as Code
Turn organizational knowledge into structured, searchable, versioned and machine-actionable information.
08
AI Context as Code
Treat prompts, policies, agent instructions, evaluation criteria and AI context as versioned engineering assets.
// coming soon
Stop clicking around. Start defining.
CloudSchool.dev is being built for engineers, platform teams, DevOps practitioners, architects and curious humans who want to understand where the “as code” mindset can take us next.
curriculum.status = "building";