GitHub Actions: CI You Will Not Fight
by Tom Eriksen
Metrics, traces, alerts and postmortems: what it takes to own a service people depend on.
TE Created by Tom Eriksen
Every bullet below is something you will have built, shipped or be able to explain by the time you finish the last lesson.
8 modules · 157 lessons · 21h of material
20 lessons running 2h 34m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
20 lessons running 2h 40m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
20 lessons running 2h 44m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
20 lessons running 2h 46m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
19 lessons running 2h 38m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
19 lessons running 2h 36m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
19 lessons running 2h 34m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
20 lessons running 2h 28m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
8 modules · 157 lessons
21h total length
Short list, and deliberately so. If you meet these you can start today.
There is a moment when a service stops being a project and becomes something people depend on. Everything changes at that point, and very little of what changes is taught anywhere. This course is twenty-one hours on exactly that transition.
Observability comes first, built rather than described. Structured logging with correlation identifiers that survive a service boundary. Metrics with cardinality you can afford, instrumented at the four signals that matter. Distributed tracing through a request that touches three services and a queue, with sampling decisions that keep the cost sane.
Alerting is treated as a design problem with a human on the other end. Service level objectives and error budgets, alerting on symptoms rather than causes, burn rate alerts that fire early enough to matter and rarely enough to be trusted, and a ruthless audit of alerts that wake people up and teach them nothing.
The second half is the human system. Running an incident with a defined commander and scribe, communicating during an outage to people who are not engineers, writing a blameless postmortem that produces changes rather than promises, sustainable on-call rotations and handover, chaos and load exercises, and the readiness review a service should pass before it is allowed to carry real traffic. A complete review checklist ships with the course.
Still unsure about something? Write to misteryjj100@gmail.com and a human answers, usually the same working day.
Nobody has reviewed this course yet, so there is no score to show. Buy it, work through it, and your review could be the one that helps the next developer decide.
Platform engineer and DevOps instructor
Tom has built delivery pipelines for teams of three and teams of three hundred, and openly prefers the smaller ones. He teaches Docker, Kubernetes and CI/CD outward from a single commit, so nothing ever appears by magic, and he treats the test suite as part of the pipeline rather than a separate subject. Every course includes a deliberate outage that you have to diagnose from logs and metrics before you can continue. He is a CNCF contributor and a reluctant but formidable YAML expert.
One-time payment · lifetime access