Design
Architecture and domain modeling
Modeling the domain, setting boundaries that survive change, and choosing an architecture that stays clear as the system grows.
about
What I do, how I work, and what I explore beyond it.

Senior .NET Developer based in Italy, using C# and ASP.NET Core to build the RESTful APIs and microservices behind real products.
I started with a bachelor's degree in Computer Science and a drive to keep learning. I like the complex problems that come with backend work, and I enjoy solving them with a team: designing clean boundaries, reviewing each other's code, and helping the people around me grow. Over the years I've contributed to large-scale systems, from the official Tokyo 2020 Olympics website to Aruba's microservices-based e-commerce platform, learning to navigate complexity, tight deadlines, and requirements that shift mid-flight. My design choices come from a simple idea: reduce the friction between whoever writes the code today and whoever will read it tomorrow, because the systems that last are the ones that stay easy to change.
Three stages of the same job: designing the system, building it, and delivering it with confidence.
Architecture and domain modeling
Modeling the domain, setting boundaries that survive change, and choosing an architecture that stays clear as the system grows.
RESTful APIs, microservices, messaging
Turning the design into ASP.NET Core APIs, microservices, and messaging, with code that's easy to review today and easier to delete tomorrow.
Testing, code reviews, CI/CD
Shipping safely with thorough unit and integration tests, code reviews, and CI/CD pipelines that catch problems before customers do - plus mentoring teammates along the way.
The languages, frameworks, and tools I reach for every day.
Primary language
Platform and libraries
Web framework
Relational database
Code versioning
Code editor
AI pair programming
Writing, side projects, and learning past the day job.
Writing slows me down and brings things into focus: technical articles and reflections on how I work, first for me and then for anyone who might find them useful.
I try out ideas, stacks, and patterns that don't fit my day job: I try, fail, take things apart, and put them back together. That's how I really learn.
Cloud and AI engineering are my next step beyond the backend: I study, work toward certifications, and run small experiments to figure out what actually delivers value.