Most payment outages don't start with bad code — they start with a reviewer who approved a PR without catching what the contract actually required. dont-break-prod is a side project built around that gap: you're handed a contract and a chunk of agent-written code, and you have to decide SHIP IT or DON'T SHIP before the PR goes out.
Get it wrong and an animated, Slack-style incident feed plays out the outage in real time — pages firing, threads spiraling — so the cost of a bad call is something you watch happen instead of an abstract warning. Get it right and it moves into a library of scenarios ranked by difficulty, with a leaderboard for teams that want to compare judgment, not just trivia.
It's a separate app from the tools here, but it comes from the same instinct: build the smallest thing that makes a real skill visible fast, without a heavyweight onboarding flow standing between someone and the point of the tool.
More from the blog
5 Habits for Debugging Messy JSON Payloads Faster
The difference between a two-minute payload review and a twenty-minute one usually comes down to a few small habits.
SQL Formatting Conventions That Make Code Review Easier
A query that's easy to review is one where the diff shows the actual change, not a reflow of every line around it.
Testing Webhooks Locally Without Exposing Your Machine
You don't need to punch a hole in your firewall to see what a provider actually sends before your endpoint touches it.