Their products targeted to other programmers seem to be nicer to work with. E.g. VS Code, C#, SQL Server. The products aimed at the ‘knowledge workers’, like Teams, and SharePoint are garbage.
So you get a pile of conflicting goals.
Generally to resolve this you need to demand a high level of user competency. Think emacs; does everything, things are mutually exclusive, competency is required.
The teams approach though is to try to satisfy this without requiring any competency. It's probably not doable
Definitely wrong, I have worked there with a few of the best developers and designers, the problem is not with the development side
> My guess would be that someone believes they need to have every feature from slack, zoom, WebEx, meet etc, and also integrate tightly with every Skype/SharePoint/OneNote feature, and also run on at least four platforms.
This is probably the main reason, probably not just with Teams but the whole Office suite
> But they aren't willing to give people time to do this.
If you refer to the above you'll see that there is never enough time to do that, it's too bloated and sometimes with contradicting requirements. If you then add testing it is probably impossible to come up with a good enough product.
Disclaimer- I still think Teams is an OK product and I use it daily