01

About

One production incident a day.

Most engineering writing is about building things. This is about the moment something built breaks in production, and about the habit of reading a system’s behaviour before reaching for a fix.

Each incident is presented the way it actually happens: a symptom, the constraints that narrow it, the evidence, and then the question. The diagnosis is withheld until you ask for it, because the part worth practising is the part before the answer.

Nothing here is a puzzle with a hidden trick. Every incident is something that genuinely happens, and every fix is one that has genuinely worked.

02

Newsletter

One incident a day, nothing else.

Coming soon: the daily send itself. Sign up above and your address is collected now, so it goes out the day there is a send worth mailing.

03

Suggest a topic

An incident you lived through beats one you think you remember.

Open an issue on GitHub and it will be picked up.