A mindset course, not a tool tutorial
Understand DevOps & DevSecOps — the way of thinking, not the toolbox
Twelve short modules that build on each other: why the wall between building and running software exists, what actually breaks when you don't remove it, and how real teams — for better and for worse — have handled it. Grounded in real case studies, not buzzwords.
The 12 modules
~105 min totalWhat DevOps Actually Is
It's not a job title, a tool, or a team. It's a way of removing the wall between building software and running it.
Systems Thinking & Flow
Optimizing your own step in the process can make the whole process slower. DevOps starts by looking at the entire flow, not your desk.
CALMS: A Lens for Diagnosing Any Team
Five letters — Culture, Automation, Lean, Measurement, Sharing — that let you look at any organization and say precisely what's missing.
Feedback Loops: Fast Beats Perfect
The single biggest lever in software delivery isn't writing better code the first time — it's finding out you're wrong faster.
Ownership: "You Build It, You Run It"
The most direct feedback loop of all is being the one who gets paged. That's not a punishment — it's the point.
Conway's Law: Your Architecture Is Your Org Chart
Software systems end up shaped like the communication structure of the organization that built them — whether anyone plans it that way or not.
Failure Is Normal: Blameless Postmortems
You cannot fix what people are afraid to admit happened. Blame doesn't prevent the next incident — it just guarantees you won't hear about it honestly.
Infrastructure as Code — the Mindset, Not the Syntax
"It works on my machine" isn't a technical excuse. It's a confession that your infrastructure isn't actually known or repeatable.
The DevSecOps Mindset
Security isn't a gate at the end of the pipeline. It's everyone's job, applied everywhere along the way — not just "shift left," but shift everywhere.
Measuring What Matters: The DORA Metrics
Years of research into thousands of teams converged on four numbers that predict software delivery performance better than almost anything else people try to measure.
Common Anti-Patterns: How Organizations Get This Wrong
Every idea in this course has a shallow, tempting imitation that keeps the name and loses the substance. Here's how to recognize the imitation.
A Quick Map of the Tooling Landscape
Now that you understand the mindset, here's just enough on the tools to recognize the names — what problem each category solves, and a couple of examples. No tutorials.
Why mindset before tools?
Docker, Kubernetes, Terraform, and the rest are implementations of ideas. Learn the ideas first — the wall between building and running software, why fast feedback beats perfect feedback, why blame destroys the data you need to improve — and every tool you encounter afterward, including ones invented after this course was written, will make sense as an answer to a question you already understand.