I wonder if part of the problem is the team's OKRs always need to include some new feature since the existence (or lack thereof) is very concrete and measurable. Of course outside of Microsoft, no one notices these features and would rather have the software simply get faster and more reliable.
Ask HN: Why is Microsoft Teams still so bad?
561–570 of 814 posts
Re: Ask HN: Why is Microsoft Teams still so bad?
#562Teams doesn't have to be good to succeed. It just has to exist. It's not even very important how good it is. Given it exists, IT will make everyone use it on Microsoft's behalf regardless of how bad it is. Or another way to look at it is that the real customers for Teams are IT departments. It makes their lives easier because they don't have to do anything and it meets all the compliance requirements they are suppose…
Someone should make job board where people can filter out companies that use Teams instead of Slack or Discord.
Slack is worse than Teams, no thanks.
Re: Ask HN: Why is Microsoft Teams still so bad?
#563Earlier quoted context omitted.
Most frustrating for me is that I receive no call notifications. Well, sometimes I do, but most of the time I do not and I need to wait until a call has been missed before I see who’s called. Unless I happen to be in the chat window of the person who’s calling…then I can see the “join call” button active. It’s maddening and IT can’t solve it properly, and I’m not the only one at my company having this issue. Utter ga…
Yeah. I log in and type "Morning" as is the routine in our main channel. Then over the next two hours I get 30 notifications about people liking my comment and nothing for anything actually useful, like calls. It doesn't even pretend to let me turn off notifications for reactions without losing the whole channel's notifications.
You can disable reaction notifications globally in Settings -> Notifications -> Chat. Doesn't help if you only want them for some channels though.
Re: Ask HN: Why is Microsoft Teams still so bad?
#564I had the joy of helping with a Teams to replace Slack rollout at the start of the Pandemic. During which I had multiple meetings with Engineers and Product folks at MS. Two reasons struck out as significant problems.
The first was that Teams is Skype and Sharepoint mashed together with duct tape. When you'd ask for improved UX, it would all fall to "Ah yes, the Sharepoint team would have to do X so the other team can do Y. They aren't built like that, though, so you cannot have it". Teams is not one product and will never feel that way.
The second was scarier. I was trying to encourage communities of practice and having open communication by default, with some private rooms when needed. Like in Slack, you have multiple channels rather than disappearing into your own Team. Promoting openness was anathema to their Product people "Why would you want people to see what you say? Privacy is the default". I got the impression MS internally is not a safe space to speak, and Teams has that same cultural baggage.
Re: Ask HN: Why is Microsoft Teams still so bad?
#565It's actually getting worse and worse even on windows sadly.
Meeting notifications are not working, and suddenly I have issues with audio which I never had before in two years. I need to unplug and plug my headphones for the mic to work.
Re: Ask HN: Why is Microsoft Teams still so bad?
#566Earlier quoted context omitted.
This. Can we use anti-trust laws to break it up?
It'd be hard to argue that MS has a monopoly on real time collaboration software when Slack exists. It'd be similarly difficult to argue they're acting anti-competitively when Slack is thriving.
I think usually the argument is that they're leveraging an _existing_ foothold to gain advantage in a _new_ market. So the existing foothold is MS Office and MS Office 360, and the new market is messaging.
How they gained this foothold in desktop productivity software is left as an exercise to the reader.
Re: Ask HN: Why is Microsoft Teams still so bad?
#567Earlier quoted context omitted.
I personally find that the more I have to use JIRA, and the more magical ephemeral rules that are set up in it to take actions in response to my actions with it, the more terrible it is to use. I've worked on teams where I just threw info into a card, and it was acceptable to use, and I've worked on teams where commits had to have a JIRA tag associated or the commit got rejected, including in instances where bitbucke…
I'm trying to cleanup a Git tree right now where people haven't put JIRA tags in their commit comments, it is impossible to find out why a change was made, it isn't a totally stupid requirement.
"It's impossible to find out why a change was made" is a completely separate issue. Either the code is documented or it's not, completely polluting your history with JIRA tags isn't the answer - not least of all because like a sibling commenter said you're now forever tied to JIRA, or if you ever move off of JIRA, now get to choose between bringing JIRA tag information into the new ticketing system, or rewriting your entire git history again.
Re: Ask HN: Why is Microsoft Teams still so bad?
#568Earlier quoted context omitted.
I'm trying to cleanup a Git tree right now where people haven't put JIRA tags in their commit comments, it is impossible to find out why a change was made, it isn't a totally stupid requirement.
Yes, "let's tie our codebase to the choice of ticket system forever as a means to commit documentation"
You can have both. Also, let's not pretend developers are wholly committed to writing comprehensive commit messages. A ticket number is useful if the change was relatively recent. If the organization moves to a different tool, chances are they are well aware of the potential history they are leaving behind.
Re: Ask HN: Why is Microsoft Teams still so bad?
#569Earlier quoted context omitted.
Someone should make job board where people can filter out companies that use Teams instead of Slack or Discord.
Slack is worse than Teams, no thanks.
I've used both. IMHO Teams is by far worse than Slack.
This doesn't mean that Slack is better than anything else, it's just better than Teams. Truth be told, even sending a letter by mail is better than Teams.