About
About
I’m a systems operator and infrastructure builder with more than 25 years of hands-on experience across the web — as an end user, a consumer, a website developer, and a system administrator. Most of what I know was earned by doing, and the lessons that stuck were the ones I had to recover from myself.
Learning the web from the inside
I got online in the late 1990s and learned the web the way a lot of people did back then — by being in it. Early on, some of that time was spent around the security side of the internet, and it taught me something that has never left: how fragile systems are when they’re poorly secured or poorly managed. I saw, first-hand and young, how easily a website or server could be knocked over when no one was paying attention to the fundamentals.
Over time my interest shifted from using the web to building it — websites, web design, hosting, and the infrastructure underneath. That shift turned out to be the whole story.
Lessons learned the hard way
The early years taught me through failure. A site compromised almost as soon as it went live — sitting on a shared server with no backups — showed me why real control over security and infrastructure matters. So I rented my first dedicated server, taught myself server administration, and never wanted to be at the mercy of someone else’s weak defaults again.
Later, a provider disappeared with almost no warning and took a lot of websites down with it. That one was permanent in its effect: it taught me not to keep all my eggs in one basket. Backups can’t live in a single place. Offsite copies aren’t optional. Use reliable, accredited registrars instead of the cheapest reseller. Build fail-safes into the work before you need them — because the moment you need them is too late to start.
How I work now
Those experiences shaped everything about how I operate: how I think about security and backups, why I care which registrar a domain sits with, why redundancy and ownership matter, and why responsive support isn’t a nice-to-have. Own as much of the stack as you reasonably can. Depend less on anyone else’s good behavior. Treat reliability as something you earn every day rather than assume.
Staying on top of new and emerging technology is part of that discipline. The threats keep evolving, so the only way to stay ahead is to keep learning — which is why I stay close to the cutting edge instead of waiting for it to catch up to me.
What I write about
These days I write about where infrastructure is heading — AI data centers, the real cost of cheap hosting, cybersecurity as an operational discipline rather than a checkbox, and what it takes to build systems that outlast a hype cycle. The perspective is practical, because I learned all of it by doing, failing, and rebuilding with better systems.