MMcpeerigan

Insights

Notes from the work.

Short pieces on operations, systems and measurement — mostly things that went wrong somewhere and were worth writing down.

Note · 22 October 2026

Your estimate was from when the job was a tenth the size

A number written once, correct at the time, quietly becomes a constraint. Ours killed two working jobs every morning and reported them as hung.

Read →

Note · 22 October 2026

A frozen feed looks healthier than a broken one

A data source that fails loudly gets fixed in an hour. One that keeps answering correctly with stale content can go unnoticed for a year, and every check you have will pass.

Read →

Note · 21 October 2026

The paywall was fine. The summary wasn’t.

Access control usually fails at the edges rather than the front door. A members-only report was correctly gated and was publishing its own contents into a tag search engines index.

Read →

Note · 20 October 2026

200 is not a page

A site returned a success code for every address we tried, including ones that had never existed. Seven required policy pages would have passed any uptime check and shown a reviewer nothing.

Read →

Note · 20 October 2026

The protection broke the thing it was protecting

A spam feature rewrote a contact address into something only a browser could decode. For the compliance reviewer who needed to see it, the page had no contact details at all.

Read →

Note · 20 October 2026

We built the checkout and forgot the paperwork

A complete, working payment system. Card handling, subscriptions, cancellation, the lot. And not one of the four documents the payment provider requires before any of it is allowed to run.

Read →

Note · 19 October 2026

It said success, and shipped nothing

A deployment reported complete, uploaded four fewer files than it was given, and said nothing about the difference. The missing part was the half that did the work.

Read →