What I built, what broke, and the evidence that changed the next decision.
No spam. No marketing. Just the writing.
Decision: routine workloads will not consume the space needed to preserve, copy, and compare a failed state. Capacity planning will include a diagnostic maneuver, not just normal demand and restart overhead.
A service doesn’t add one generic maintenance task. It adds work at every dependency boundary where its assumptions can diverge from the next version underneath it.
Replacing a scheduled path is deceptively simple. The old job runs on a clock, the new worker reacts to a richer trigger, and both appear to perform the same task. It’s tempting to disable the old entry, enable the new one, and call the migration complete when the first run succeeds.
A container management screen can make one small change feel harmless. Select a running service, adjust an environment value, click redeploy, and the new behavior appears. The repository remains untouched. No syntax to remember, no file to open, no review needed.
A listening port is a wonderfully low bar. It proves that something accepted responsibility for an address. In local model infrastructure, that can happen well before the system is capable of doing the job that brought a caller there.
CEOs say AI isn't moving the needle on productivity. I've been running AI in production for months. Here's why they're both right and wrong — and what the actual measurement problem is.
Three years ago my homelab was a Raspberry Pi running Pi-hole and a Plex server. Today it's a multi-node cluster handling production workloads for paying clients.
I've been running large language models locally for a few months now, and honestly? I'm not going back to API-only workflows. The Cost Math Cloud
Laying the foundation for my homelab rebuild with MicroK8s. This post covers why I chose it, how I configured it, and how my Ansible admin node (Overseer) keeps everything repeatable.
A behind-the-scenes look at how I designed and segmented my UniFi network—covering VLANs, Wi-Fi strategy, firewall rules, and how each subnet fits into my homelab and home life.