Colophon

What the write-ups are

Project overviews, not essays. Each one summarises a piece of infrastructure work: the constraint, the approach, the measured outcome. They’re written so someone assessing whether I can do a job can see what I’ve actually run, at what scale, and what the tradeoffs were.

They’re not written to be enjoyable. If you want the version with jokes in it, buy me a beer.

Drafting

Some pages were structured with the help of a large language model (Claude, Anthropic — 2026). The pattern is: I supply the facts, decisions, numbers and outcomes; the model helps with structure and phrasing; I check and rewrite.

Pages drafted this way carry a note at the top. Pages without a note were written directly.

Everything factual is mine either way — the architectures, the numbers, the decisions and the mistakes. Where I don’t have a figure to hand, I say so rather than estimating.

Technical

Hugo, hand-written templates, no theme. Self-hosted JetBrains Mono. No analytics, no trackers, no third-party requests.

Source lives on my own Forgejo instance. Pushing to main fires a webhook at the host, which pulls and rebuilds. About one second end to end.

Hosted on YunoHost on ARM64.