Software engineer. Problem solver. Professional rabbit-hole explorer.
I’ve spent my career building software without paying much attention to whether the work was called frontend, backend, infrastructure, DevOps, or whatever new label the industry invents next. If it needed building, understanding, fixing, or occasionally unbreaking, chances are I’ve done it.
Some days that meant designing user interfaces. Other days it meant APIs, databases, Docker containers, CI/CD pipelines, or figuring out why a server had decided that 3 a.m. was the perfect time to develop a personality.
I’m curious by nature, which is both my greatest strength and the reason I have a homelab that has absolutely no business existing.
I enjoy understanding how things work. Not just enough to use them, but enough to explain why they work, where they break, and what trade-offs their creators had to make. That’s probably why I gravitate toward open-source software. I like being able to look under the hood, run things on my own infrastructure, decide when they update, and keep my data somewhere I actually control.
I also have a healthy skepticism for hype. Every year there’s a new framework that’s going to change everything, a new AI model that’s supposedly replacing developers, or a revolutionary architecture that’s destined to become next year’s legacy code. Sometimes the hype is deserved. Most of the time, it’s just marketing with better graphics.
This blog isn’t a programming tutorial, a productivity guide, or an attempt to become a thought leader—whatever that means. It’s simply a place where I write about things I find interesting. Sometimes that’s software engineering. Sometimes it’s AI, self-hosting, privacy, automation, or an open-source project I’ve been tinkering with. Sometimes it’s an opinion that refused to stay inside my head.
If you happen to enjoy wandering down the same rabbit holes, welcome. You’re in good company.