I understand the problem before writing code
Functional analysis is not a formality — it is where a project is won or lost. Years on both sides taught me that the most valuable code solves the right problem.
I build systems that scale, analyze them with business judgment, and lead them with team vision. 7+ years doing it.
// HOW I THINK
Functional analysis is not a formality — it is where a project is won or lost. Years on both sides taught me that the most valuable code solves the right problem.
Nine years of graphic design before code are not a detail — they are why I never lost sight of the user. The interface is the product for whoever uses it.
Architecture that cannot be maintained or scaled is not an achievement, it is a problem. I design systems and write code that can be maintained, scaled, and self-managed by clients through CMS and other content systems.
Testing is not the last step — it is the only honest way to know if what I built delivers what I promised. I review as a user, not as the author.
// WHAT I BUILD WITH
In a world where technology advances every day, my stack is the result of years of experience, learning, and adaptation — with the goal of keeping on learning and improving my skills.
// CONTEXT
7+ years in technology, starting as a systems administrator and functional analyst through to leading development of large-scale internal systems with end-to-end delivery. That teaches you to build things that actually have to work, with real teams and users who cannot afford mistakes. Today in the private sector, I bring that same judgment to every project.
$ git log --oneline --graph
$ CONTACT --OPEN
We can talk. No forms