CI, CD, and deployment pipelines
By the end of today you can describe what should happen automatically between a push and production, write a pipeline that runs your checks, and explain how a bad deploy is undone.
YesterdayOn Day 50 you built an image that runs identically anywhere. Today something else builds and ships it for you.
TomorrowTomorrow, the configuration that makes the same image behave correctly in each environment.
Why this matters
A pipeline is where the quality bar becomes enforced rather than hoped for. It is also the difference between deploying nervously once a month and deploying calmly several times a day.
- Continuous integration
- Continuous deployment
- Pipeline ordering
- Rollback
Learn it
80 minCopy this into Claude or ChatGPT. It quizzes you before it explains anything, which is deliberate. The resources under it are how you check what it told you.
Today's Master Prompt
Free · sign inA prompt written for this day alone: your level, the exact scope, what to leave out, and an instruction to quiz you before it explains anything. Paste it into Claude or ChatGPT and it teaches you today's material.
Check it against something that is not a model
An assistant can be fluent and wrong, and on a topic you met today you will not catch it. These cover the same ground and were made by people who do this for a living, so they are what you hold the explanation up against. They are other people's work and we only link to them, so judge them for yourself.
3 hand-picked resources
Free · sign inVideos, official docs and articles covering the same ground, each opened and annotated by hand. They are what you check the assistant against on a day you cannot yet catch it being wrong.
Build it
50 minWrite a pipeline for your API that runs lint, type checks, unit tests, builds the container, then runs integration tests against a real database service. Order the stages so the cheapest fail first. Then deliberately push a change that fails type checking and confirm it stops before the expensive stages.
Recall it
20 minAnswer out loud, reveal, then mark honestly whether you had it. That score is the only thing on this page you do not get to choose.
5 recall questions
Free · sign inQuestions you answer from memory, then grade yourself against the real answer. The score is carried into the mastery rating below it, so an honest miss cannot quietly become a tick.
Rate it
Completion and mastery are tracked separately. Be honest, because an inflated rating only means the concept resurfaces sooner.
Mastery tracking
Free · sign inRate yourself against five named criteria per concept. Completion and mastery are tracked separately, and anything you rate shakily comes back automatically on a spaced schedule.
Recap
- 01The pipeline is where the quality bar becomes enforced rather than hoped for
- 02Cheap checks first, so failure arrives in seconds not minutes
- 03Code rolls back easily; migrations are what make it hard
- 04Smaller, more frequent deploys are safer, not riskier
Your progress
Free · sign inMark days complete, pick up where you left off across devices, and watch completion and mastery diverge. Free, and the account exists only so ninety days of work cannot vanish with a cleared browser.