The person behind the systems.

It didn’t start with software

My interest in technology goes back much further than the point where it became a profession.

School science projects introduced me to circuits, sensors and microcontrollers. Watching a few lines of code make something real move across a desk felt incredible then. It still does, honestly.

Over time, software became the centre of that interest, and I went on to study computer engineering. Most of my professional life now revolves around building software, but writing code is not the part that excites me most. What I care about is watching an idea slowly turn into something that works.

Sometimes that is a large web application, sometimes a mapping system or a small electronic circuit. Sometimes it is an unnecessarily demanding weekend project that began with a simple question: could I build this?

What I do today

Professionally, I work mainly in product and frontend engineering with React and TypeScript.

Over the years, I’ve had the chance to work on a wide range of problems: data-heavy interfaces, complex workflows, rule-driven systems, real-time operational tools and map-based applications.

Frontend is my main area of expertise, but I’ve never thought of myself as someone confined to the browser.

If a problem reaches into a desktop application, maps, a 3D environment, an API, an embedded system or a physical prototype, that is still part of the game for me.

What I enjoy most is finding structure inside problems that initially look messy. I like building systems that appear simple to the user while carrying serious machinery underneath, designing them so they can grow over time and, when necessary, being willing to rethink them from the ground up.

The habit of making things

I don’t put much distance between myself and technology outside work either.

Robotics, embedded systems, electronics, 3D printing and DIY projects have interested me for a long time. I’m especially drawn to systems that can sense their surroundings, make decisions and move autonomously.

That might be a drone, a ground vehicle or something travelling underwater. The platform matters less to me than the idea of a machine understanding its environment well enough to act within it.

My personal projects can be small, experimental or far more specific than any reasonable person would ever need. They usually begin with the same question: “Can I build this?”

If I don’t know the answer, I research it. If I’m missing some knowledge, I learn it. If I need a part, I find it; if I need a model, I draw it; if I need code, I write it.

Sometimes the result is genuinely useful. Sometimes it only teaches me a few things that will become useful in the next project. Either outcome is enough.

Away from the screen

Life, of course, is not only about engineering.

Music has been an important part of mine for a long time. I’ve played piano for about ten years and also spend time with the electric guitar. It is one of my favourite ways to use a part of my brain that works a little differently from the engineering side.

Photography and film matter to me as well. I shoot with a Lumix S5IIX, occasionally experiment with short films and enjoy working through light, framing and atmosphere as much as the technical side of the image.

Science fiction, horror, games, films and carefully built fictional worlds probably influence me more than I realise. There is a reason I keep returning to the darker worlds of Edgar Allan Poe and H. P. Lovecraft.

I think all of this shapes the way I consider rhythm, feeling, interaction and visual coherence, even when I’m building something deeply technical.