cookbook

Infrastructure, as a game

Break it.
Fix it.
Learn why.

Short browser games where a cluster fails, a build crawls or a state file drifts, and you fix it with the real commands. Every incident links to the note that explains it.

  • 3 games live
  • 11 levels
  • 0 installs, runs in your browser
deploy/web · 6 replicas
83%

        
Tap a crashed pod to delete it.

The board

One game per topic. Ten are live.

Each game models a real tool closely enough that the commands transfer.

Scores and completed levels are saved in this browser only.

How a game teaches

The loss is a pointer to the page you needed.

  1. An incident arrives

    A pod crash-loops, a layer cache misses, a CI job leaves a lock behind. The board shows the symptom, not the cause.

  2. You diagnose and fix it

    Use a real prompt: kubectl describe, docker build, terraform plan. Reading is free; changes cost a move.

  3. The log explains why

    Each resolved incident links to the exact note section behind it, so you can read the theory after you have felt the problem.

Event log · Drift Detective, day 4
day 4 · open A crashed CI job left the state locked Error: Error acquiring the state lock
Who: ci-runner@deploy-812
day 4 · resolved Lock cleared with force-unlock

Confirm nothing is really running, then terraform force-unlock LOCK_ID.

Learn why: Drift and locking, in practice

Notes

Prefer to read first?

The notes are short, and every example in them is built, applied or deployed in CI on each change, so the commands work.