Skip to content

DevOps

Shipping safely and often: pipelines, environments, rollouts.

GitCICDpipelinesenvironmentsTerraformsecretsblue-greenrollingcanaryfeature flags

Lessons

  1. 10.1Git, branching and code reviewHow a team of people can change the same code every day without stepping on each other, and why small changes win. 30 min
  2. 10.2CI/CD pipelinesAn automatic assembly line that checks every change and carries it safely to real users, so releasing becomes boring. 30 min CI/CD pipeline
  3. 10.3Infrastructure as codeInstead of clicking around a cloud console, you describe your servers and networks in files, and a tool builds exactly that. 30 min
  4. 10.4Deployment strategies: recreate, rolling, blue-green, canary, shadowSome releases will be bad. Here are five ways to swap old code for new so a bad one stays small and short. 30 min Deployment strategies
  5. 10.5Feature flags: separate deploying code from releasing featuresPut code on the servers today, switch it on for users whenever you like, and switch it off in seconds if it misbehaves. 30 min Deployment strategies

On the job: try it on your own project

Ask Claude Code to walk you through your CI/CD pipeline file step by step: what runs on each push, what blocks a merge, how a change reaches production and how it is rolled back. Time a full run. Write a one-page release map, mark the slowest step and the missing safety check, and propose one improvement on a branch.

Can you do this now?

0/4. Anything you can't tick yet: reopen that lesson's practice ladder.