About

I did my Bachelor's first, then went to manage a restaurant because the money was good and it seemed like the sensible thing to do. I stayed three years. It taught me a lot about coordinating people and solving problems in the moment, with no option to defer them to tomorrow, but it also made it obvious over time that I was drifting away from the thing I actually wanted to be doing. So I went back and started the Master's.

My first real project came earlier, during my Bachelor's internship: a website that tracked a city's buses on a map, built with the Google Maps API. No AI, no shortcuts, just working out how to make an API and a map behave the way I needed. That was the one that made it click, seeing something you wrote turn into a thing people could open and actually use.

Since then the projects have gotten bigger. A VR training simulator built with a rehabilitation association, now published and presented at two congresses. A SaaS product I led as CTO at an accelerator, from architecture to production. A full-stack app on a microservices architecture. Work across web, mobile and games, because I've never wanted to be boxed into one layer of the stack.

What ties them together is that I'd rather ship something people actually use than build something technically clean that nobody touches. That's also how I think about AI: it's a tool that lets me move much faster, but the architecture calls, the security decisions and the responsibility for what ends up in production stay mine. I'm currently rewriting that first tournament app I built by hand years ago, and the gap between the two versions is the clearest measure I have of what's changed.