How I got here

I did not grow up thinking I would be a programmer. I just kept finding things I wanted to try on a computer.

Sometime around 2005, my father came home with our first computer. I don't remember the day clearly, but I remember wanting to use it all the time. Before we had internet, I spent a lot of time in Encarta, jumping between maps, photos, articles, and short videos.

When we got internet, I started learning from forums and YouTube tutorials. That is how I found Sony Vegas, through people on the internet explaining just enough for me to follow.

I made exactly the kind of videos you would expect. Photos, music, text on the screen, dramatic transitions with no restraint. A few might still be on YouTube, which is both funny and a little terrifying.

Photoshop came next. Around 10 or 12, I edited photos of friends, made banners, changed colors, and probably overdid all of it. Then I started wanting a camera. I read about ISO, aperture, and shutter speed before I even had one. Later, my parents bought me a Canon 70D when I was around 16 or 17. I still have it.

One of the first times photography felt real was a medieval festival in my hometown. Some of those photos were later displayed near the local museum and the citadel. It wasn't a grand exhibition. But for me it was huge. Photos I had edited at home were suddenly outside, where strangers could stop for a second and look.

In my last year of high school, I started making websites. I think the editor was Brackets. I wrote pages by hand, mostly HTML and CSS, changing a few pixels, refreshing, and doing it again until it felt right. There was no agent to build a full React app with a backend in five minutes. If I finished a small website in a day or two, that felt fast.

I had programmed before that in high school, writing C++, even pointers, but it mostly lived in the console and felt like homework. Websites felt different. They were visual. Someone could open what I made and click around. That changed something for me. Code was no longer only an answer printed in a terminal. It could become something someone used.

University made programming feel more serious, but I still learned by building small projects because I was curious and impatient. I wrote Python scripts, browser automations, and little scrapers because I couldn't stand doing the same clicks over and over again. They were small and rough, but they did the job. Funny enough, it was an early version of what I ask agents to do now, just with more deterministic code and patience.

During the pandemic, classes moved online and I had more time at home than usual. I got curious about machine learning, but the examples felt too abstract, so I used the Champions League to make it real. I gathered match results, team stats, form, rankings, and built a small model to predict games. It was around 56 or 57 percent accurate. Not genius, but better than a coin flip, so I was proud of it.

Later I got curious about Bitcoin and blockchain because the technology felt different from anything I had used before. That led me to smart contracts and then to my bachelor project, where I used an NFT as a kind of digital twin for a vehicle. Ownership, service history, metadata, all the things that usually get split between PDFs, websites, and papers in a glovebox. The project was early, but I still liked the idea that blockchain could make messy real-world records easier to trust.

That project got me a free ticket to a blockchain conference in Paris. I met the Itheum founders there, stayed in touch, and ended up working in blockchain for the next few years. I worked on smart contracts, SDKs, infrastructure, and developer tools. The daily work was much less glamorous than the conference version of the story, but I learned a lot.

After that, I joined Fast. Most of my work here has been around agent tooling, AI harnesses, and systems that give AI the context and tools to act.

Building also brought me to San Francisco, most of it in a hacker house. I had worked with teams before, mostly remotely, but being around people building all day felt different. The pace was higher. Conversations turned into ideas quickly. I left sharper, more ambitious, and with a better sense of what a good day of building can look like.

When I'm not working, I ride road bikes on country roads and sometimes race. It is my main hobby and probably the easiest way for me to clear my head after too much time in front of a screen.

I like being around tools while they are still a little undefined. Agents feel like that right now. They are messy and sometimes unreliable, but also useful enough that I can't ignore them.

My parents brought home a computer, and the internet helped me teach myself. I kept learning, building, and following whatever made me curious until it became my work.

I am proud of that.