My Story

If you ask me when my journey into software began, I could point to a programming language, a project, or the first time I built something that worked.

But that wouldn't really be the truth.

The truth is that I didn't find engineering because I had everything figured out. I found it while trying to figure myself out.

Like most people, my path hasn't been a straight line. There were years that challenged my confidence more than my ability. Expectations didn't always become results. Plans changed. People came and went. There were moments when I questioned whether I belonged where I was headed at all.

Looking back, I'm strangely grateful for those moments.

They taught me something I probably couldn't have learned any other way: progress isn't built on perfect conditions. It's built by continuing anyway.

Somewhere along the way, software stopped feeling like a subject to study and started feeling like a way to create. I became fascinated by the idea that a few lines of code could solve a real problem, help another person, or bring an idea into existence that didn't exist the day before.

That curiosity slowly became the constant in my life.

Since then I've had the privilege of working on enterprise platforms, AI systems, government research, secure communication frameworks, hackathons, startups, and far too many late-night ideas that never made it past the whiteboard. Some succeeded. Some failed. Every one of them taught me something worth carrying into the next.

Today I spend most of my time building software, reading about systems, sketching ideas that are probably too ambitious, and asking questions that usually begin with "What if...?"

I'm particularly drawn toward problems involving distributed systems, artificial intelligence, cybersecurity, and products that live beyond a prototype.

Outside engineering, I enjoy writing, reflecting, and occasionally stepping back long enough to appreciate how far a curious mind can travel when it refuses to stop learning.