About

I build technology around problems worth solving.

I’m a software engineer and technical lead with more than ten years of experience building software across large enterprise systems, startups, industrial products, and my own projects.

I started my career focused on one question:

How do I become a better software engineer?

Over time, that question became broader.

  • Who has the problem?
  • Why does it matter?
  • What should actually be built?
  • How will people use it?
  • How does it fit into the wider system?
  • And can it create something valuable?

Today, I work at the intersection of technology, people and business.

My first years at Amadeus taught me reliability, testing and what it means to change systems where mistakes can have real consequences.

Later, working in startups and industrial environments pushed me beyond implementation.

I became increasingly interested in architecture, user experience, product decisions, domain knowledge and how teams make good technical decisions together.

That evolution changed the way I look at engineering:

The code matters. But so does everything around the code.

Building MyEasyTransfer and later CoGarden pushed that thinking further.

I experienced what it means to start with a problem, design a product, build it, deploy it and then face the much harder question:

Will anyone actually use it?

That taught me something I now consider fundamental:

Building software is often easier than building a business around it.

Marketing, distribution, trust, pricing and customer acquisition can matter as much as the product itself.

AI is changing software development quickly.

I use it extensively, but I’m more interested in what it changes than simply how much faster it makes us.

  • What happens when software can be generated faster than we can read it?
  • How do we preserve understanding, quality and responsibility?
  • And if implementation becomes cheaper, do product judgment, creativity and understanding the customer become more valuable?

Those are some of the questions behind what I write about and experiment with.

I enjoy gardening, puzzles, baking and walking.

A surprising number of my ideas start away from the computer.

I like activities where you observe, make small adjustments and gradually understand how the whole system behaves.

I’m still deeply technical.

But I’m increasingly interested in problems where technology is only one part of the answer.