5 ms·
It isn't because Microsoft lacks good programmers. My guess would be that someone believes they need to have every feature from slack, zoom, WebEx, meet etc, an
by fancyfredbot 4y ago
It isn't because Microsoft lacks good programmers. 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. But they aren't willing to give people time to do this.
- peterfarkas 4y agoThis is spot on. I remember thinking that they added so many features very early on, even though they were still struggling with the most basic ones. And it sounds like they still do.
- mysterydip 4y agoWhen I end a meeting, Teams helpfully shows a window that states something like "meetings is just one of the many things we do!" to which I want to reply, "maybe you shouldn't do more".
- cjbgkagh 4y agoThat’s what they get for consistently paying less than other FANG companies.
- mr_toad 4y ago> It isn't because Microsoft lacks good programmers. 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.
- psnehanshu 4y agoI wonder how there's so much difference. Don't programmers working at VS Code and Teams interact with each other?
- rawoke083600 4y agoCould very well be that the PM/PO of the VSCode project has actual dev-experience as well ?
- psnehanshu 4y agoI read somewhere else that VS Code is maintained by the GitHub team, is that correct?
- 2rsf 4y ago> It isn't because Microsoft lacks good programmers. 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
- kristopolous 4y agoIt's software that has never said no to a feature. 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