Here's who I am...

Programming

I started building things because of open-world games — GTA V most of all. In middle school I opened Unity for the first time to make one of my own, and that's where my life as a developer began. What I fell in love with wasn't the game; it was the act of taking a problem or principle from the world, modeling it mathematically, and watching it come alive inside a machine.

In college that fascination shifted toward services — web and apps. While serving in the military, at a base 800m up a mountain, I taught myself Next.js, React, and Tailwind in the evening hours we were allowed online. Shipping something useful, fast, had its own kind of catharsis. I wanted to be the developer who turned ideas into working software quickly.

By the time I was discharged, the world had changed: generative AI had arrived. The thing I had been good at — shipping software, fast — was no longer scarce. I started a frontend job with Claude open beside me, and the unease grew sharper. For a while I doubted whether building still meant anything I could call my own.

What pulled me back was the first paragraph. What I had loved as a kid wasn't shipping; it was abstraction — rendering the world in code. So I chose to live as a researcher. The shipping skill didn't disappear; it became the other hand of the same craft. Today I think of myself as a researcher who can build UX-aware software fast, with AI as a multiplier rather than a threat.