About me

I studied mechanical engineering for both my bachelor's and master's degrees, where I used computational fluid dynamics in my graduation theses. That work pulled me into the world of programming, and I became a software engineer simply because writing code was fun.

Over the last about three years as a software engineer, I've realized what I really enjoy is not just coding, but building systems. I care about how to make a system stable and scalable, and how to design it so that new teammates (and even AI agents) can join the project smoothly.

Along the way, I've found that I care as much about the working environment as the code itself. I enjoy writing clear READMEs so people can understand and participate quickly, designing unit-testable structures to reduce risk, and using tools like Docker and docker-compose to keep local and deployment environments predictable. My current company has no dedicated DevOps team, so I've gradually taken on more of that responsibility and I'm interested in growing further in that direction.

Today I focus on system design for real-time systems. Every component should have a clear reason to exist, which makes the architecture easier to understand and gives everyone a shared sense of why things are done this way. If you'd like to see how I apply these ideas in practice, you can find a few of my recent projects on the Projects page.