I started as a full stack developer, but after three years I crossed over to the backend side: no cookies, no pixels, just pure logic. And I never looked back.
Over the next 8 years I worked on projects that ranged from the straightforward to the genuinely complex. I designed and maintained custom CMS systems, defined database architectures for enterprise-level projects, and built API platforms that kept different ecosystems talking to each other, including integrations with management software and SAP.
Some of the work I'm most proud of sits at the intersection of backend and data: automated data analysis systems in Python for e-commerce platforms, a tracking system for product service interventions, and a pipeline that extracts data from PDFs to generate mechanical exploded views and manage spare parts requests, the kind of problem that sounds simple until you're actually solving it.
These days I've traded the IDE for a different kind of architecture: I'm now a Project Manager at Studio Zerotredici, where eight years of getting my hands dirty in the backend translates into knowing exactly what's realistic, what's risky, and how to keep a project on track.
