About

I keep a small home lab and an even smaller amount of patience for undocumented changes. This site is the compromise between the two.

Why a logbook

Every home lab reaches a point where the operator becomes the single point of failure. Not because the hardware is fragile, but because the reasoning behind a decision evaporates in about six weeks. A dated note beats a perfect memory, and it beats a diagram that nobody updated after the second rebuild.

So the rule here is simple: if a change took more than an hour, or if I had to look something up twice, it gets a note. If the note turns out to be wrong later, the correction goes at the bottom with its own date instead of quietly rewriting history.

How the notes are written

Commands are shown as they were actually run, including the flags I would have skipped if I were being clever. Numbers come from the machines in this room and are not benchmarks of anything else. Where a vendor name shows up it is because that is what is bolted in the rack, not because anybody is paying for the mention.

The measurement you did not write down did not happen.

Technical shape of this site

Plain HTML and one stylesheet, served as static files. No trackers, no fonts fetched from elsewhere, no comment widget, no build step worth the name. It loads on the tethered phone connection in the garage, which is the only performance target I care about.

Contact

Corrections are welcome and get credited. There is no form on this site by design; if you know me, you know where to write, and if you do not, the notes should stand on their own.