A small Proxmox estate, a second-hand desktop with a 6GB GPU, and a set of agents doing real jobs every day. No theory, and no benchmarks in a vacuum — the numbers, the failures, and the settings that actually fixed them.
Six-page PDFs, A4. Written to be followed, not admired — plain English, every term explained the first time it appears.
A job that fails loudly is an annoyance. A job that stops running is invisible. Four ways one dies while the logs still look fine — and how to verify by effect instead.
February 2026 renamed and removed parts of the Web API, which is why almost every tutorial you will find is now wrong. What moved, what vanished, and how to read the errors it returns instead.
Two pages of A4. The reference card version of the guide above it — for pinning up, not reading through.
The four silent failures, what to check for each, and how to verify a job by its effect rather than its logs.
Every rename side by side with what you were taught, and how to read 403, 404 and 429 correctly when the path is the real problem.
Field notes and packaged copies of work that is open source anyway. Take them for free; pay if they saved you an evening.
Five trading bots that reported every action as a success while doing almost nothing — and what rebuilding them taught me.
One identity provider in front of a whole self-hosted estate: what worked, what broke, and the zero-cost mistake that undid most of it.
Moving scattered credentials into one self-hosted secrets manager — the one-home principle, and scoped machine identities.
Fitting a GPU to a ZimaBlade: the slot's undocumented limits, the driver trap, and how to diagnose it when the card crash-loops.
Nine files on running a ZimaBlade like a server rather than an appliance — including backups that include your certificates.
Only when something has actually been measured and written up. No schedule, no newsletter cadence, and nothing forwarded from anybody else.