About me.

I’m a software engineer who spends a lot of time thinking about systems — not just how they work, but why they break, scale, recover, and evolve the way they do. Most of my background revolves around cloud infrastructure, containerization, observability, distributed systems, and performance analysis, but I’ve always been the type to go down rabbit holes far beyond whatever my job title says.

Lately, I’ve been building projects around monitoring, scaling, and infrastructure because I enjoy understanding the moving pieces underneath modern applications. I like turning complex technical ideas into things people can actually visualize and learn from. Outside of engineering, I’m usually in the gym, researching something obscure at 1AM, working on my car, or figuring out how different systems behave under pressure.

I’m big on continuous learning, experimentation, and building things that make people stop and say, “Wait… that’s actually really cool.”

Currently Reading

• Vert.x in Action – Reactive systems and asynchronous architecture.
• The Goal – Systems thinking, bottlenecks, operational flow.
• Researching – MPLS, distributed systems, AI infrastructure, observability.