I wrote my first website at 13. Not because of the market — because building something from nothing felt like the most powerful thing I could do with a computer. That conviction never changed.
I did not come to development following a career path. I came because building things produced something few activities do: the sensation that thought becomes real. HTML, CSS, JavaScript — a language for giving shape to ideas. Over time that language became more complex: architectures, APIs, databases, infrastructure. But the motivation is the same.
Today I lead projects where code is only part of the problem. I understand why a product is built, for whom, and what impact it has. That changes how you design the architecture, how you prioritize features, and how you make decisions under pressure. I do not execute specifications — I co-design systems.
My ambition is to build products that not only work, but last. Systems that can be maintained, scaled, and understood. To lead technical teams where clarity of thought is as important as skill in code. And at some point, to found something of my own — a product where technology, design, and business vision converge in an original way.
I do not follow trends. I build foundations.