Hello. This is the obligatory first post, and like every first post it has to answer one question: why does this site exist?
The short answer: I build infrastructure for a living and I kept telling myself I should write things down. The long answer is about twelve years long, so let me give you the medium one instead.
Who is writing
I have spent those twelve years building and occasionally rescuing infrastructure: networks, servers, storage, and the platforms on top. These days that means designing AI datacenters and enterprise systems by day, and running a small Kubernetes cluster at home by night, where ideas get tested before anyone has to pay for them. This site is served from that cluster, which means every post you read here survived my own infrastructure first.
Why a blog, why now
Because the notes are piling up. Twelve years of fixes, designs, and lessons live in my head, my chat logs, and a frightening number of markdown files. It is time some of it lives in public, where it might save someone else a bad weekend. That is the whole agenda: build things, write them down, share the useful parts.
What to expect
Casual writing, mostly. The plan, loosely:
- Build logs. Real infrastructure work with real configs and real error messages, because sanitized examples never break the way real ones do.
- Lessons learned. Short posts about mistakes, so you can skip making them yourself. I have a healthy backlog.
- AI engineering. Agents, memory systems, and making LLMs do useful work in a real environment instead of a demo.
- Project docs. When something I build is worth using, its manual goes up under MAN_. The first one is already there.
First proper series coming up: how the home cluster came to be. It involves retiring a hypervisor that served me well, three mini PCs, distributed storage on hardware that has no business running it, and exactly one moment where DNS for the whole house went dark because of me. That story starts soon.
Thanks for stopping by. The lights in the living room flicker occasionally. Now you know why.