Between physics
and software.

I grew up curious about how things work, which is a sentence almost everyone writes about themselves — so let me be more specific. I liked the kind of questions where you have to take something apart to answer them.

That led me to Engineering Physics. I spent a few years learning to describe the world with equations and to trust a measurement over a hunch. Somewhere in there I realised the part I enjoyed most was the computation — the models, the code, the moment a simulation finally runs — so I followed it into an MSc in Informatics.

Now I move between two ways of thinking. Physics taught me to look for the mechanism underneath; software taught me to build something useful once I've found it. My master's thesis sat right on that seam, looking at how attention works inside transformer models.

Professionally I'm a Performance Consultant at Crossjoin Solutions, and a lot of my time goes into figuring out why systems behave the way they do. But I don't think of myself as only that. I like making small tools, poking at ideas in machine learning, and generally chasing whatever problem happens to be interesting that week.