Colophon
Walter wrote this site. I decided what shipped.
That claim is on the front page, so it should be backed up somewhere. This is that page.
Walter is the command center this practice runs on. It holds every project's context, keeps a memory that prunes and resurfaces itself, and directs today's best models as instruments. There's a longer explanation of it here.
Walter built this website. It read the source of the tools being described, pulled the real numbers out of those repositories, chose the structure, wrote the markup and the stylesheet, and drafted the words. It writes the notes as well.
I set the direction, edited the result, argued with some of it, and pressed merge. Nothing reaches this site that I have not read.
What that does and doesn't mean
It is not unsupervised
Every change ran the same gauntlet as client work: static analysis, automated code review, and models from rival labs cross-checking each other, because different labs have different blind spots and the disagreements are where to look. Reviewers advise. None of them can push a commit.
The review caught real things
On the build before this one, review caught a claim on the Sentry page that was simply too strong, and a file that would have published internal notes at a public URL. Both were mine to sign off on and both were wrong. The gauntlet is not decoration; it is the reason this approach is defensible at all.
The numbers were verified, not recalled
Test counts and analysis levels on this site were read out of the actual repositories rather than remembered. One long-standing figure could not be reproduced and was reduced to what could be proven. If a number here is wrong, that is a bug, and I would like to know.
Why say so at all
Because the argument this whole site makes is that good tooling plus a human who owns the result produces better work, faster. Hiding the tooling while making that argument would be a strange way to make it.
The unglamorous specifics
Hand-written PHP with no framework, no CMS, and no build step. One stylesheet of plain CSS on a custom property system. A little vanilla JavaScript. Clean URLs come from real directories rather than rewrite rules. The notes are flat files; there is no database anywhere on this site.
Type is DM Sans and JetBrains Mono. Colour contrast was checked numerically against WCAG AA rather than by eye, which is how the link colour ended up changing: the previous one was passing by a margin too thin to be comfortable.
It is hosted on a small server, deploys when a pull request merges, and is fast because there is almost nothing to it.
Want this pointed at your problem?
The same machinery that built this site in an afternoon is what builds the client work. That is the entire pitch.