Thanks for the feedback - we actually just shipped this. There's now an interactive security bug challenge right on the landing page. No signup, just click the lines you think have issues and check your answers.
You're right that the role is shifting toward AI orchestration. We'd argue that makes code review skills more important, not less - someone still has to catch the bugs in what the agents produce.
A fun simulation game of prod breaking where you have to race to troubleshoot and fix the issue. Great for SREs, devs devops, founders and teams to learn in a non prod environment but feels real.
This is a great distinction. Right now all our scenarios are postmortem replay - you're dropped in after things have already gone wrong. But a pre-incident mode where you're reviewing a setup and have to spot the misconfiguration before it blows up is a really interesting idea. Different skill, equally important. Adding it to the roadmap.
Thanks! SadServers is great - love what Fernando built there. The main twist here is that the scenarios are built from real postmortems rather than generic server puzzles. The terraform one is modeled directly on the Claude Code incident from last week.
Thanks for trying it out! Just pushed a fix - there was a bug where the game engine wasn't starting properly after clicking GO. Should work now. Create a free account and give it another shot, would love to hear how you do.
If you followed the Claude Code terraform incident last week - Claude Code ran terraform destroy on production, took down 2.5 years of course submissions - you probably read Alexey's postmortem and the 500+ comment HN thread about it.
What struck me reading the postmortem wasn't the destruction itself. It was the decision chain: no remote state backend, deletion protection disabled, a Terraform archive from the old machine sitting there with full production state. Claude actually flagged the risk at multiple points. The human approved the destroy anyway.
I built a playable version of that session. You sit in a split-panel Claude Code interface - terminal on one side, AI agent on the other - and work through the recovery. The scenario uses the same kind of setup that caused the original disaster. It takes about 10-15 minutes.
This is part of YouBrokeProd, a browser-based incident response trainer I've been building. 10 scenarios total built from real postmortems - connection pool exhaustion, Kubernetes crashloops, DNS failures, SSL expiry, and others. Three are free including this one.
Stack: Next.js, Turso (SQLite at the edge), Supabase Auth. Each scenario is a state machine - you run commands, get realistic output back, form a hypothesis, and submit a diagnosis and fix. Scored on speed, accuracy, and efficiency.
The hardest part has been writing log output that's realistic enough to teach something but designed well enough to actually be solvable in 15 minutes. Curious what the SRE folks here think of the tradeoff.
You're right that the role is shifting toward AI orchestration. We'd argue that makes code review skills more important, not less - someone still has to catch the bugs in what the agents produce.
reply