I’m nugg3tz.
I come from IT — networks and security. That’s the lens I build everything through, whether it’s a server in my own house or somebody else’s website.
My day job is in physical security and distribution. It’s the unglamorous kind of work where a system that fails quietly is worse than one that fails loudly, and it taught me to design for the moment things go wrong. That turns out to be most of what engineering actually is.
Everything else I learned at home, on my own hardware. I run a homelab on a single machine — one physical node, four virtual machines split by function: a gateway, home automation, media, and game servers. Remote access is zero-trust, so nothing management-facing is exposed to the internet. The whole thing is infrastructure-as-code: I can tear it down and rebuild it from scratch with one command, and I have. Backups run nightly to a separate NAS, and the containers report their own health back into Home Assistant through sensors I wrote.
That last part is how the Home Assistant components started. I needed something, it didn’t exist, so I built it — and then published it, because if it was missing for me it was missing for someone else. They’re open source now, some already in the HACS default store, the rest waiting on review.
Websites are the same discipline pointed at a different problem: read the spec, handle the failure cases, ship something that keeps running when nobody’s watching it. The difference is that a site also has to be worth looking at — and that’s the part I enjoy most.
No agency, no middlemen, no account manager. You talk to the person who actually builds it.
Websites, tools, automations — tell me what you need and I’ll quote it.