When I joined my current employer, a few years ago, one of the things I thought might be good was that for the first time in a fairly long career I'd be using Visual Studio.

Previously I'm a vi or vim user for everything, for many years.

But I can say after a few years experience I'm not really impressed. It's too big and too slow. It has a few things I kinda like, a lot of half-working things I'd love if they worked consistently (e.g. some things I work on can be debugged, some can't, experts might know why but I don't) but as they are they're too unreliable to really change how I do things - but overall it's not enough to e.g. miss VS when I'm writing my own stuff, still in vim on Linux.

Actually all of the Microsoft technologies I've run into were disappointing with only two exceptions which I'll get to. Powershell felt like they hadn't really learned the right lessons from the Unix shells for example, and Entra ID (called "Azure Active Directory" when I started caring) is a confusing mess.

Two exceptions: 1. C# is a pretty good language. Mostly it's a better Java. Is that amazing? Not really, but it's still pretty good, it delivers reasonable performance, there's a large ecosystem, I don't hate writing it.

2. Azure itself has to have a way to "cut off" payments because Microsoft sold a product where students can get a limited amount of credit. The student doesn't have any money, so if they had $50 of Azure credit and Microsoft lets them spend $85 before turning off all the Azure systems that credit was funding, well, too fucking bad - Microsoft eats the $35 loss. Accordingly Microsoft are better (not perfect, but better) than AWS or Google's thing at actually turning stuff off when it exceeds what you asked to spend.