Why I still enjoy building with .NET
A personal take — not a framework war, just what keeps me productive.
I'm not interested in framework holy wars. Use what fits the team, the constraints, and the decade the system needs to survive. That said, I keep choosing .NET for professional work — and it's worth articulating why without pretending it's perfect.
Predictability over novelty
ASP.NET Core gives me a clear request pipeline, first-class dependency injection, and conventions that scale across teams. When six people touch the same API, shared patterns matter more than expressive one-liners.
The SQL Server reality
A lot of my work sits next to large relational databases. EF Core isn't always the answer, but the ecosystem around data access, migrations, and tooling is mature. I can drop to raw SQL when I need to without fighting the platform.
Tooling that respects professionals
Visual Studio and Rider are unglamorous and effective. Debugging, profiling, and refactoring support reduce the friction of working in large solutions. I'm faster when the IDE understands my project structure.
It's not static
Modern .NET is cross-platform, performant, and actively evolved. Minimal APIs, source generators, cloud-native templates — the platform moved while some critics weren't looking.
Would I use something else for a greenfield side project? Maybe. But in regulated enterprise environments where reliability and hiring matter, .NET keeps earning its place on my machine.
That's a personal preference, not a universal law — and I'm comfortable with that.