Learn DevOps
Start here if DevOps is a word you use more confidently than you would like.
What does the Learn DevOps track cover?
This track covers what DevOps actually means as a working model, the practices that carry most of the weight, what to automate and in what order, and how to tell from measurement whether any of it is working.
The route, in order
A definition that survives contact with practice, and the misreadings that reduce it to a job title.
DevOps, continuous delivery, SRE and platform engineering, defined and distinguished.
Ordering automation by repetition multiplied by the damage of doing it badly.
Keeping every change releasable, and why batch size determines everything else.
The integration cost nobody puts on the slide, on either side.
DORA metrics, why they are reported as a set, and what happens when they are not.
What you should be able to do afterwards
- Explain DevOps without reaching for the infinity diagram
- Identify which stage of your own delivery path to automate first
- Distinguish continuous delivery from continuous deployment, and say why it matters
- Read DORA metrics as a set rather than as four separate numbers
Questions about this track
No. DevOps predates Kubernetes and applies to virtual machines, managed platforms and serverless equally. Start here and take the Kubernetes track afterwards if it is relevant to your environment.
The reading is around forty minutes. Applying it to your own delivery path is the part that takes time, and it is the part that matters.
Where to go next
Learn Kubernetes
For people who have to run Kubernetes, not just deploy to it.
Learn observability
What each signal is for, how to make them join, and how to keep the bill sane.
Learn DevSecOps
The controls that reduce the most risk, in the order worth doing them.
Learn AI and agentic DevOps
Where agents genuinely help, where they are oversold, and how to introduce them safely.
Learn cloud operations
Running infrastructure across providers without three of everything.
See it working rather than reading about it
Connect a cluster read-only during a demo call and look at the concepts in your own environment.