Curious about howsoftware behavesafter it ships.

Most of my experience has come from building things that eventually need to run in the real world—not just inside a local development environment.

That means my work often goes beyond writing application code. I find myself thinking about architecture, deployments, servers, APIs, databases, debugging, users, and the small operational details that decide whether a product actually works.

I got interested in programming by pulling apart small personal projects to see how they worked, and that curiosity about what's actually happening under the hood has stuck with me since.

I'm most drawn to problems where software has to hold up against real usage — inconsistent networks, concurrent users, data that doesn't arrive in the order you'd like — rather than problems that only need to work once, in a demo.

Right now most of my time goes into building and maintaining production systems, and I'd like to spend more of it on projects where I own the problem end-to-end, from the first design decision through to how it behaves in production.