Build log

What broke, and what I changed because of it.

Not advice. Incidents with dates on them, the theory I held before I understood the problem, and the rule I kept afterwards.

· 3 min read

Exit code zero is not evidence

A deploy that reported success every time and changed nothing. The signal everyone trusts is the one signal that cannot detect this.

Read it

The build log, by mail

New notes, when I publish them.

One mail per note: what broke, the theory I held before I understood it, and the rule I kept afterwards. Irregular on purpose — I write these when something happens, not to a schedule, and I would rather send you nothing than send you filler.

Your address, nothing else. Not sold, not shared, and never used to sell you anything you did not ask about. Reply “stop” to any of them and I take you off.

Recognise any of these in your own stack?

That is usually the point at which a teardown pays for itself. Five days, fixed price, findings in writing.

Get in touch