3 ms·
Years ago I started with a .NET shop as a junior dev not because of the language or tooling, but because the job and company were a good fit. Since then I've d
by uticus 3y ago
Years ago I started with a .NET shop as a junior dev not because of the language or tooling, but because the job and company were a good fit.
Since then I've done other languages for personal projects, but have made a career out of .NET development. There are things I don't like about the language, sure, but the backing of MS, the very large user base, and the ability to use on non-Windows systems have outweighed everything.
So I'm not the biggest fan by any means, but I do recommend as a prudent decision over most other options from a business point of view.
- EMM_386 3y agoFor my first software engineering job, I was hired to replace a Microsoft Access system that had grown too big. I decided to just write it in .Net with SQL Server, since that's what Microsoft was saying to do at the time. That was 22 years ago, when it was in beta. I've also made a career out of it. I got to greenfield another project recently, and I went with C# for the APIs.