// notes
What I changed, and why.
Decisions from real work — including the ones I got wrong the first time and had to go back for.
These are working notes, not articles. A note gets written when something is decided and the reasoning is worth keeping: a problem in a build, a claim that turned out not to hold, a thing that looked finished and wasn't.
Each one is dated. There is no schedule and none is promised — they appear when there is something to say rather than on a calendar. If you want the long, fully-sourced version of an argument, that lives in the articles instead.
A check that has never failed is not a check you have tested
Two of my own checks were reporting PASS while looking at almost nothing, and the broken samples built to catch that were green too.
2 August 2026 · 2 min read
ReadThe form said it was on its way and sent nothing
Three defects in one contact form, and the worst of them only fires for people who use a password manager.
1 August 2026 · 3 min read
ReadNine services became four
The services page listed nine things. The about page said the angle was deliberately narrow. Both were on the same site.
1 August 2026 · 2 min read
ReadIf something here is relevant to a job you are weighing up, that is a good reason to get in touch.