How the day job shows up in the lab
The current role is senior identity and access work: Microsoft Entra, federation, Conditional Access, and tenant-wide administration for a hybrid directory. Before that I led desktop and infrastructure support, and before that I was the person who opened the chassis, kept the repair notes, and escalated the cases that did not fit a script. The blog is not a dump of ticket comments. It is the same habit applied to Linux I run at home.
When I write a CoreOS Quadlet, I am doing what I do at work with a service account. One job, a unit file, a restart policy, and a firewall that defaults to closed. When I write an Omarchy install guide, I am doing what I do with a workstation image. Document the first boot, the update path, and the three ways it fails, so the next person, usually a future version of me, does not rediscover them from a black screen.
Identity work also explains the tone. I care about who can reach a port, which password unlocks a disk, and what happens when a laptop leaves the building. Encryption on by default, BitLocker turned off before a dual-boot shrink, and an admin UI that is not bound to the world are the homelab version of that. They are not aesthetic preferences.
What goes into a guide
I install the thing. I keep the commands that worked. I write down the command that looked right and was wrong. I do not publish frame-rate tables I did not measure on the machine in front of me. If a number matters, it is a version, a port, a timer, or a checksum from the upstream release, and the post names that release.
Videos on the channel are the companion. The post is the page you can search. A description box is a bad place to keep a kernel parameter. If you watched an Omarchy 4 episode and you want the steps, the first-week guide is the page to keep. The comparison posts are for the decision, before the USB is flashed.
I would rather link a narrow article than paste the same procedure into three roundups. The nomodeset ISO rebuild, the Resolve AUR workaround, the Silverblue virtualization layer, and the Quadlet firewall each earned their own URL. The experience of maintaining this site is mostly deciding which URL a sentence belongs on.
The machines, on purpose
The desk is a daily-driver Linux desktop. Lately that is Omarchy when I want a Hyprland session without building it from the wiki. Fedora is the release I leave alone for a month: a jumphost, a mutable workstation, or an XFCE spin on older hardware. Fedora CoreOS is the appliance. DNS, a Quadlet, Ignition, and no compositor. Alpine is the tiny host, an old laptop running Docker for Pi-hole or Jellyfin.
That split is how I keep the lights on, and it is how the tags are organized. A search for Omarchy should not dump you into a Pi-hole unit file. A search for Podman should. The about page is the longer biography. This page is the method, then the sponsors, then the resume.
Corrections, tutorial questions, and business notes go to thelinuxitguy@gmail.com.