About / Contact
Hi, I’m Alex.
I’m a Technical Team Lead who likes building useful software—and understanding the whole path from a button in the browser to the machine doing the work.
Last reviewed
On this page
What I bring
My current professional title is Technical Team Lead. The home projects documented here give me hands-on experience across systems administration, application development, Linux operations, automation, and troubleshooting. I’m interested in the seams: where a frontend needs better failure states, where a backup policy conflicts with storage placement, or where a deployment process hides what is actually running.
The projects here are practical examples. I build and maintain them for people who use them, with real hardware constraints and a continuing maintenance responsibility.
How I work
- Make the system understandable. Clear boundaries, useful diagrams, and recovery instructions matter as much as initial setup.
- Prefer evidence to labels. A container being healthy, a backup completing, and a user workflow succeeding are different claims.
- Keep people in control. Interfaces should be predictable; agent contributions should be reviewable.
- Use maintainable tools. Open systems and locally auditable components make investigation and long-term ownership easier.
Home Assistant, Proxmox, Caddy, and the other open-source foundations do substantial work. My contribution is the custom software, integration, operational design, and ongoing care described in these pages.
Let’s talk
If you’re hiring for systems administration, infrastructure, automation, or a role connecting operations with application development, I’d be happy to discuss the work.
For a quick introduction, start with Hearth. For a technical conversation, try the thin-pool incident, the inference gateway, or Workbench’s review boundary.