Why another tech blog

There are enough tech blogs. Most of them are either content marketing wearing a hoodie, or tutorials rewritten from other tutorials by people who never ran the thing in production. I want this site to be neither, so it seems fair to say up front what it is.

Notes from actually running things

Everything I write about here, I run. The homelab posts come from hardware in my house that everyday life at home depends on. The company posts come from the ventures I build and operate; I introduced them in who I am and on the about page. When I write about a deploy pipeline going wrong, it is because my deploy pipeline went wrong, not because the topic scores well.

That has a practical consequence: posts appear when something happened, not on a schedule. Some will be short, some a full postmortem with config excerpts. None of them will be “10 tools you need in 2026”.

Opinions included

I am not going to pretend infrastructure is politically neutral. Where your data lives, who can switch your services off, and whether you can leave a platform are political questions, and running your own infrastructure is one answer to them. This site has a politics tag and I intend to use it. Expect arguments about infrastructure and dependency, not party politics.

If you only want the config files, skip those posts. They will be clearly tagged.

Self-hosted, no tracking

This site practices what it preaches. It runs on my own infrastructure, and there is no third-party tracking on it: no analytics scripts phoning home, no fonts loaded from someone else’s CDN, no cookie-banner theater. You read, I write — that is the whole transaction.

What to expect

Homelab and networking write-ups, notes on building small companies, and the occasional argument about digital sovereignty. If that sounds useful, the about page has the overview of who is writing, and the archive will fill up from here.