My journey in mobile development started long before Flutter existed.

I've worked with everything from C++ and OpenGL to native iOS and modern cross-platform applications. Different technologies, different challenges — but the same curiosity about how things work.

Today, I combine hands-on development with architecture and technical leadership. I enjoy writing code, solving difficult problems, and making things simpler rather than more complicated.

Engineering Principles

Simplicity is a feature.

I believe good architecture should make development easier, not introduce unnecessary complexity. I prefer straightforward solutions that are easy to understand, maintain, and evolve.

Understand the problem first.

Before choosing a technology or designing a solution, I try to understand the actual problem. Sometimes the best technical decision is to write less code.

Think beyond the implementation.

A solution isn't finished when the code works. I care about how it performs, how it's tested, and how easily another developer can change it six months later.

Keep questioning decisions.

I don't believe in following patterns or best practices blindly. Every decision has trade-offs, and understanding them matters more than choosing the most fashionable approach.

People & Leadership

Lead by example.

I believe leadership starts with actions, not titles. I stay involved in technical discussions, code reviews, and implementation. I wouldn't ask my team to follow practices I'm not willing to follow myself.

Create clarity, not control.

My role isn't to make every decision for the team. I focus on making goals, priorities, and expectations clear, giving developers the freedom to find their own solutions.

Find the root cause, don't just escalate the problem.

When facing a problem, I try to investigate and understand its root cause before escalating it.

Build trust and ownership.

I believe people do their best work when they feel trusted and responsible for what they build. I encourage open discussions, different opinions, and constructive feedback. Good ideas can come from anyone on the team.

Encourage ownership.

I value people who aren't afraid to take responsibility, tackle challenging problems, and take risks to find solutions. Even if they can't solve a problem entirely on their own, what matters most is what they learn along the way.

Help people grow.

I see code reviews, technical discussions, and everyday collaboration as opportunities to share knowledge and learn from each other. Helping someone become a stronger engineer is just as rewarding as solving a difficult technical problem myself.

Beyond Engineering

Life isn't all about code. I enjoy playing guitar, football, and reading. But with a big family, finding time for all of that is a challenge of its own!