In 2021, I spent a week staring at Haskell stack traces and firewall logs trying to figure out why my Cardano relay node wouldn't sync.
No AI assistant. No perfectly matching answer anywhere online. Just documentation, forum posts from 2019, and the kind of stubborn patience that either breaks you or shapes you.
I was running a Cardano stake pool on Linode: a block producer and two relay nodes. I had never provisioned cloud infrastructure before. I barely knew what I was doing. But I understood enough to know I wanted to figure it out.
The firewall rules were a mess. Registering pool metadata to the exchanges and analytics platforms was more opaque than it had any right to be. The Haskell-based cardano-node software threw cryptic errors that sent me down hours-long rabbit holes through topology config files and port bindings I'd gotten wrong.
And then one morning, something changed.
The relay nodes came online. Connections started flowing in.
Japan. Canada. Brazil. The UK.
Peers from across the world were connecting to infrastructure I had built, on machines I had provisioned, behind network rules I had written. I watched the peer list populate in real time and thought: this is exactly what I want to do for the rest of my career.
Building the Foundation
I had been in IT for a few years at that point: first supporting a school district, then working at a local managed services provider. Good foundational work that taught me how systems actually break in production. But it wasn't until I saw those global connections light up that I knew exactly where I belonged.
I went after my CCNA and passed. That opened the door to a Network Administrator role at Spectrum, where I was quickly promoted to Network Engineer. I kept studying while working full-time and earned my ENCOR, then my CCNP Enterprise. The deeper I got into enterprise networking, the more I noticed the edge of the network was shifting.
Networks don't stop at the perimeter anymore. I needed to move with them.
Where I Operate Today
For the past several years I have been working at the intersection of enterprise networking and cloud infrastructure. It is a space most engineers approach from one side or the other. I have operated from both directions simultaneously, and that dual perspective changes everything about how you design systems.
One of my core responsibilities has been designing and maintaining secure hybrid connectivity. That means IPSec tunnels, BGP route propagation, and segmentation policy between on-premises data centers and cloud environments running in AWS and Azure. This type of work requires you to think like a network engineer and a cloud architect at the same time, and mistakes at that layer have real consequences in healthcare environments where uptime is non-negotiable.
Beyond connectivity, I have been part of migration work that goes deeper than lift-and-shift. We containerize workloads and deploy them onto managed Kubernetes services, refactoring on-premises servers into PaaS in the cloud. Once you have rebuilt infrastructure that way, you cannot unlearn it. It permanently changes how you think about what a server actually is.
Why AWS. Why Now.
Because the timing has never been better, and I do not want to waste it.
We are living through what I believe is the golden age of self-directed technical education. The same AI tooling that is reshaping how infrastructure gets built is also reshaping how engineers learn. I can go deep on an unfamiliar topic faster than ever before. I can stress-test my understanding against real scenarios, get targeted feedback in minutes, and iterate across a full study session rather than across days.
Compare that to 2021: alone with Haskell documentation, manually cross-referencing forum threads hoping someone had hit the same firewall issue two years earlier. The contrast is not subtle.
But here is what I would never trade about learning the hard way: I built the ability to actually troubleshoot. To hold a complete mental model of a system under pressure. To persist through genuine ambiguity until something works. That skill does not come from having answers handed to you. It is what separates engineers who can direct AI tools effectively from engineers who simply depend on them.
The AWS Solutions Architect certification is the next deliberate step in aligning my credentials with the work I have already been doing. I have been designing and operating in these environments for years. I want formal validation of that depth, and I want to close any gaps that emerge along the way. That combination of hands-on experience and structured certification is exactly what makes an engineer credible at the architecture level.
The stake pool is long gone. It ran for a while, earned a few delegators, and I shut it down when the economics of small independent pools made it unsustainable.
But I still think about those relay nodes coming online. Watching peers connect from Japan, Brazil, the UK. The feeling of seeing something you built reach out across the world and find other machines.
That is still what drives me. It always will be.
Building hybrid cloud infrastructure or hiring engineers who bridge enterprise networking and cloud? Let's talk.
Connect on LinkedIn