My path
-
Elmec Informatica S.p.A.
Full stack developer
October 2025 — presentDevelopment of internal products, tools used every day by colleagues in a company of around a thousand people. A .NET backend with Entity Framework Core, a Vue frontend with TypeScript, data on SQL Server.
- Work set up around GitOps: the content of the repository is the truth the environments mirror, and releases go through CI/CD pipelines that stop when the build fails or the automated checks do not pass. Every version arrives with notes and documentation kept up to date.
- Internal applications owned end to end: analysis of the operational and business requirements, frontend and backend development, deciding how data is used and stored, testing with the end users, going live, and fixing the bugs that daily use brings out, tracked through the ticketing system.
- Continuous improvement of the existing portals, bringing them in line with the conventions agreed by the team: moving data access from stored procedures to Entity Framework Core, adopting the shared libraries instead of repeated code, uniform logging and testing, .NET framework and frontend dependency upgrades, server-side pagination and REST APIs consistent with the standard.
Highlights
-
Centralised email delivery
Every product used to send its email its own way: templates written inside the code, recipients configured by hand, and if a message failed nobody knew. I put all of it into a single NuGet library, with the templates in Scriban, and now every internal product we build uses it. On top of it I am building a service with a UI of its own, where templates will be written and tested without needing a release, and delivery will go through a RabbitMQ queue that retries by itself when something goes wrong.
-
Design system rebuild
Led the visual overhaul of the shared component library, the one every internal product we build depends on, and introduced dark mode in it. I also handle the migration of the projects that use it: I go through the interface with whoever maintains them and advise on what to change and how.
-
Frontend internationalisation
Introduced the idea of internationalisation. The texts live outside the Vue components, so the day another language is needed there are no whole pages to rewrite.
-
Università del Piemonte Orientale
Computer science
October 2023 — presentI study part-time alongside my full-time job.
-
Gruppo SBS
IT and full stack developer
2019 — 2025IT department of Vapriounit, the group’s electronics industrial site in Vaprio d’Agogna, northern Italy, serving six of its companies: Ekinex, Sitec, Telestar, Renovis, QOC Solutions, Integra. User support and development of the internal tools, with PHP, Vue and C#.
- First, second and third level helpdesk: maintenance and support on colleagues’ computers, remote sessions included, setting up new workstations, managing accounts and permissions in Active Directory, hardware inventory, network infrastructure administration, support on bugs and new requests for the applications.
- The only developer in the department: on every internal tool I handled the requirements, the frontend and the backend, the data schema, the testing with the people who would use it, the releases to production. The architecture decisions I worked out together with my manager.
Highlights
-
Ticketing and ERP integration
An open source ticketing and inventory platform adopted, with a few plugins written to fit, and connected to the company ERP through custom APIs: customers and items stayed in sync with a single source of data, with no double manual entry.
-
Bespoke internal portals
Company portals built as WordPress themes written from scratch, with PHP and Vue for the application layer and Bootstrap for the interface. They showed the ERP data up to date (revenue, orders, sales, the main customers) and hosted the day-to-day tools, like the production schedule. The CMS already provided users, permissions and administration, maintained and patched by an active community of contributors. Also developed a solution in Laravel, outside the CMS, in a case where the stack and the architecture had to be custom, for precise integrations and more flexibility.
-
Scheduled syncs and checks
Syncs between systems and automated checks, scheduled to run at fixed intervals. One example is a C# service that queried the European Commission’s VIES API every day and flagged the customer VAT numbers no longer valid, a check that until then was done by hand, one at a time.