Homelab
The homelab exists because production environments are a terrible place to learn.
In production, every change carries a cost. You’re working inside someone else’s constraints, against someone else’s timeline, with someone else’s tolerance for risk. You learn what you can, but you learn carefully, and you don’t always get to finish the thought.
At home, you get to finish the thought.
What the homelab is for
It started as hardware rescue — old Macs and ThinkPads given a second life running Linux, partly because it’s interesting, partly because throwing away a machine that still works seems wasteful. That’s the YouTube channel, mostly: the things I’ve disassembled, revived, and documented.
The more technically serious use is the lab environment for work I can’t easily do anywhere else. The Oracle WebCenter OVA post and the WebCenter 14c lab build are the clearest examples — a controlled environment where I could reproduce the production system’s behaviour without the production system’s consequences.
The hardware projects
The video collection is the homelab in its most visible form: Mac Pros from 2008 running modern operating systems they were never intended to run, a ThinkPad X220 that continues to be a better laptop than most things sold in 2023, a Synology NAS that turned into a multi-part series about whether vendor-mandated drive requirements constitute greed (they do, probably).
These aren’t guides. They’re documented experiments, with the dead ends left in. YouTube Content
The philosophy
There’s a version of homelab content that’s really just consumption — the next piece of hardware, the next OS install, the next benchmark. That’s not what I’m after.
The homelab is useful to me when it produces understanding. When the experiment answers a question I had about a production system, or gives me a safe environment to test an assumption before I act on it. The hardware is just the medium.