
The Person Behind the Code
Half Italian, half Swiss. Fully committed to whatever I do.

My Story
I started coding in Rome in 2010, building e-learning platforms and even consulting for the Italian Ministry of Defense. What began as curiosity quickly turned into a calling. I moved to Switzerland in 2013 and never looked back.
Over 16 years I've worked across industries that couldn't be more different — insurance at AXA, retail at Migros, finance at Vontobel and a major Swiss bank, private banking at Union Bancaire Privée. Each one taught me something new about how technology serves people and business.
Today I lead a frontend chapter of 13 engineers at a major Swiss bank. But leadership to me isn't about titles. It's about getting things done, bringing people together, and making sure we don't waste time on things that don't matter.
How I Work
I'm a doer. I don't enjoy endless meetings or over-engineered solutions. I like understanding the real problem, finding the simplest approach that actually works, and driving it to completion. "Make sense" isn't just a motto — it's how I evaluate every decision.
I bring both hard and soft skills to the table. I can architect a micro-frontend system from scratch, and I can also align a team of strong-willed engineers around a shared vision. I've learned that the best technical solutions mean nothing if the team isn't on board.
I see the bigger picture. Whether it's restructuring a codebase, defining a company's frontend strategy, or mentoring junior developers into confident engineers — I connect the dots between technology and business goals.
What Drives Me
Impact Over Activity
I measure success by outcomes, not hours. Every line of code, every meeting, every decision should move the needle.
People First
Great software is built by great teams. I invest in people because that's what scales.
Simplicity Wins
The best solution is the one you can explain in a sentence. Complexity is easy — simplicity takes discipline.
Technical Philosophy
I believe the best code is the code you don't write. YAGNI isn't just an acronym I like — it's a filter I apply to every decision. Before adding a layer of abstraction, a new dependency, or an extra service, I ask: do we actually need this today? Nine times out of ten, the answer is no.
I follow the Rule of Least Power: use the simplest technology that solves the problem. If HTML and CSS can do it, don't reach for JavaScript. If a static page works, don't build an SPA. This isn't about being anti-technology — it's about respecting the complexity budget of every project.
I've seen too many teams burn months on frameworks they didn't need, abstractions that made things harder, and patterns borrowed from blog posts that didn't fit their context. My job is to cut through that noise and build things that actually work — today, not in some hypothetical future.
Beyond the Screen
When I'm not coding or leading teams, you'll find me outdoors. I love camping and biking — the kind of activities that reset your mind and remind you there's a world beyond pull requests.
I'm based in Switzerland but I carry Italy with me. The passion, the directness, the refusal to accept mediocrity — that's the Italian half. The precision, the reliability, the love for well-structured systems — that's the Swiss side. Together they make someone who cares deeply about quality and isn't afraid to push for it.
I stay curious. I read broadly, experiment with new tools on personal projects, and always try to understand the why behind the how. That's how I ended up writing blog posts comparing Java BFFs with fullstack Node.js, or building forms with zero frameworks just to see what the browser can do natively.