The personbehind the products.

My career started with web design and development. At the beginning, my focus was on making things work and learning the technology behind them. With every project, the questions became bigger.

Those questions gradually changed the way I worked. I moved from designing and building individual pieces to taking a much broader view of the product, the technology and the business behind it.

After working on enough products, you start noticing patterns. Requirements are not always clear. Designs do not always answer every question. Technical decisions made early can become expensive later. And a product can be technically impressive without actually solving the problem it was supposed to solve.

That experience changed the way I approach development. Today, I try to understand the problem before reaching for the solution. I think about the product, the people using it and the people responsible for maintaining it.

I don’t want every project to feel like a list of tasks that gets handed over and forgotten.

Good work usually comes from having enough trust to ask questions, disagree when something doesn’t make sense, communicate problems early and take responsibility when things become difficult.

If we’re working together, I want you to know where things stand, what needs attention and what I’m thinking about. My goal is not simply to finish my part. It is to become someone you can rely on when the product needs to move forward.

A successful project should make the next project easier. Once I understand a product, a business and the way a team works, I can contribute with much more context and much less friction.

That is why I value long-term relationships with founders, businesses and agencies.

I enjoy working with people who care about what they are building.

It could be a new product, an existing platform that needs serious improvement, a business that needs better technology, or an agency looking for someone dependable to own development.