Why I Bet My Engineering Career on .NET 9 (And Left Legacy PHP Behind)
Source: Dev.to
My Journey from Legacy PHP
When I started my journey in software engineering, I spent a lot of time in the trenches of legacy web development. I maintained spaghetti PHP codebases, patched SQL injection vulnerabilities in systems used by thousands of students, and wrestled with the chaos of loosely typed languages. It was a necessary education, but it wasn’t the future.
Why .NET 9 and C#
Today, as a Software Engineer based in Verona, I have pivoted entirely to the Microsoft Stack (.NET 9). C# gives me the strictness I need: if the code compiles, it (mostly) works. The transition from legacy PHP to a strongly‑typed language changed the way I think about data. I no longer just move JSON around; I define Models, Contracts, and Interfaces, making the software predictable and secure by design.
Blazor WebAssembly
With Blazor WebAssembly, I can write C# on the server and C# in the browser. This eliminates the constant context‑switching that “Full Stack” used to require—switching between a backend language (Python/Java) and a frontend framework (React/Angular). A single language stack simplifies development and reduces runtime errors like “undefined is not a function”.
Enterprise Adoption in Italy
There is a reason enterprise companies in Northern Italy (and the world) run on .NET: it is stable, fast, and mature. I come from a background of low‑level automation and WinAPI optimization, so I care about milliseconds. .NET delivers the performance and reliability needed for large‑scale CRM architecture and other mission‑critical systems.
You can view my portfolio and projects at .