The Audit Log Nobody Reads Until They Need It
Most weeks nobody looks at Magatama's audit log. That's exactly why I built it properly.
Magatama watches my server fleet and diagnoses problems without me in the loop. Getting it to admit when it doesn't know turned out to be harder than getting it to sound smart.
Most weeks nobody looks at Magatama's audit log. That's exactly why I built it properly.
Magatama won't touch a fix unless it matches a document I wrote by hand before the problem happened. Here's what actually goes into writing one of those.
Why I stopped trying to write one big autonomy roadmap for the agent that watches my home and cloud servers, and started treating it as six separate, permanently unfinished strands instead.
I'm testing whether a language model running on my own hardware can do a better job suggesting conference introductions than the tag matching NOGnet already has. So far I mostly have questions.
I've been chewing on whether the trust someone earns at one NOG event should mean anything at the next one, and I don't have this worked out yet.
Most of what a NOG community remembers about its sponsors, speakers, and program gaps lives in one volunteer's head until that person steps back and takes it with them. NOGnet keeps a thin layer of notes attached to each profile so some of that memory survives the handoff.
Why every NOGnet module is built to be pulled out and embedded elsewhere instead of requiring anyone to adopt the whole platform, and what that discipline costs a solo developer building it alone.
On building the sponsor-support module for NOGnet, and discovering that organizers don't need a better pitch document. They need a way to track who to talk to and when.
A look at the unglamorous, unpaid judgment work behind NOG conference programs, and an honest account of what NOGnet's PC-support tooling can and can't replace.