The Homelab as Creative Outlet: Why I Keep Building Things Nobody Asked For
I run a Proxmox cluster in my basement. It hosts the QA for this website, a Plex server, a Pi-hole instance, some Docker containers I'm experimenting with, and an Ansible-managed configuration that I've rebuilt from scratch at least three times. By any rational economic analysis, I could host all of this in the cloud for less money and zero maintenance overhead, but I keep the homelab anyway.
The reason isn't technical. It's psychological. The homelab is the one environment where I get to be an individual contributor again.
The IC Itch
Three years removed from hands-on technical work, I still have the builder's itch. The desire to configure something, troubleshoot something, make something work that wasn't working before. At work, my job is to enable other people to do that. I remove blockers, set priorities, advocate for resources, and develop engineers. It's fulfilling work, and I don't want to go back to IC permanently. But the absence of building with my own hands creates a gap that nothing in the management role fills.
The homelab fills it. When I'm configuring a new container, writing an Ansible playbook to automate a deployment, or troubleshooting why a VM won't boot after a storage migration, I'm using technical muscles that atrophy without exercise. The work doesn't matter to anyone except me, and that's precisely what makes it valuable. There's no stakeholder, no deadline, no one waiting on the output. Just the satisfaction of making a thing work.
The Tinkerer's Permission
There's a version of this hobby that becomes unhealthy (another obligation, another thing to maintain, another source of guilt when it's neglected). I've been in that mode before, where the homelab felt like a second job and "I should be working on the server" competed with family time. The boundary that keeps it healthy for us is simple: the homelab is a leisure activity, not a commitment. If a month goes by without touching it, that's fine. If I spend a Saturday afternoon rebuilding my Docker stack because I feel like it, also fine.
The permission to be inconsistent with it is what keeps it sustainable, and it's the same reason I keep my hobbies unmonetized in general. This isn't a production environment with SLOs. It's a sandbox. Things break and stay broken for weeks. Experiments fail and get abandoned. The point isn't reliability. The point is creative engagement with technical problems on my own terms.
What It Gives Back to the Day Job
It's funny in retrospect how often homelab work has directly informed my professional decisions. When I rebuilt my Proxmox cluster with Ceph storage, I encountered failure modes that gave me better context for evaluating a vendor's storage pitch at work six months later. When I automated my entire configuration with Ansible, I developed opinions about role structure and variable management that shaped how we standardized our team's automation approach. The learning isn't wasted because the domains overlap.
I'd never frame the homelab as professional development (it's a hobby, and insisting otherwise ruins it), but the transfer of knowledge is real. Having hands-on context with the same technologies my team works with means I can ask better questions in design reviews, spot assumptions in architecture proposals, and understand the operational implications of technical decisions in a way that pure-management experience wouldn't provide.
The Creative Loop
What I've come to understand is that the homelab serves the same function as guitar practice, or designing shirts for the Commissary, or writing for this site. It's a creative outlet. The medium happens to be infrastructure rather than music or visual design, but the psychological function is identical to what I see with Minecraft and hackathons: I'm producing something, seeing it work, feeling the satisfaction of the made thing.
For anyone in a management role who feels the IC itch, I'd encourage finding your version of this. It doesn't have to be a homelab. Maybe it's a personal coding project, maybe it's contributing to open source, maybe it's building automations for your own household. The specific medium matters less than having a space where you build things without organizational overhead, where the only standard is your own satisfaction, and where failure is free.
The Setup (Because Someone Will Ask)
Current state: a three-node Proxmox VE cluster running on a mix of old desktops, Ceph storage and old synology for shared VM disks, a dedicated pfSense VM for network segmentation, and everything managed via Ansible from a private Git repo. Total power draw is around 110W. Total monthly cost is under $15 in electricity. The whole thing fits on a single shelf in my basement utility room, next to the networking gear.
Oh, the family Minecraft server also lives here. That one might have a bit of an uptime SLA to it, unofficially of course.