Live data from Hacker News

The Horror of Microsoft Teams

medium.com

101–110 of 344 posts

Re: The Horror of Microsoft Teams

#101
My company is switching to Teams right now, because Slack “does not have active directory integration”.

I asked them if it wasn’t a better idea to just enable that then, but apparently the ability to actually use any corporate software is just not very high on their list...

Re: The Horror of Microsoft Teams

#102
post #94

At my work, we use Teams a fair bit, and I'll go out on the limb to defend it (a limb I'm quite familiar with at this point ;) ). Thinking of it as a Slack alternative is, IMO, the wrong starting point. We barely use it for chat (as we have Slack as well). Instead, we use it as a file share and central information home. Each group within a team has a channel and we use the tabs to track meeting notes, embed external…

So essentially Microsoft's chat app is not good at chat, but you use it for file-sharing instead because Microsoft's file-sharing app is not good at file-sharing?

It's good at chat. It's not good at persistent chat rooms.

It's great for ad hoc groups of people to chat or for direct chat. It's also great for meetings. Where it gets cumbersome is in the persistent chat room management.

And as someone who is not a fan of chat rooms as a replacement for emails (I can't even filter or categorize information) I'm glad about that part.

Re: The Horror of Microsoft Teams

#103
At my org, you'd never know that slack has muting as an option. @here in a nontrivial channel gets you public humiliation, every possible "loud" reaction thrown at you (to the point of hitting the slack limit on reactions) and people publicly scolding you that you just notified 500 people in 12 different time zones.

Re: The Horror of Microsoft Teams

#104

Earlier quoted context omitted.

Slack and Teams are different. Slack has muting. Teams does not.

Teams has mute on channels

On individual channels it does, on an entire team it doesn't. You can mention a team itself (rather than a channel in that team) and there's no way to mute that afaik.

Re: The Horror of Microsoft Teams

#105

Earlier quoted context omitted.

That's correct. The company where I am currently working at was using Slack but recently decided to stop paying for Slack and instead use Teams since they were already paying for a subscription to Office 365 for each employee. I hate it. My colleagues hate it. The UI is terrible. Most of the time navigating between the channels is a pain and the UI is just horrendous. I think the funniest thing that was released late…

>The emojis are of bad quality and look like crap. Maybe an oversite on my part, but I didn't even consider this as I was evaluating an enterprise productivity app...

An ugly and unpleasant working environment can affect your productivity.

Re: The Horror of Microsoft Teams

#106

At my work, we use Teams a fair bit, and I'll go out on the limb to defend it (a limb I'm quite familiar with at this point ;) ). Thinking of it as a Slack alternative is, IMO, the wrong starting point. We barely use it for chat (as we have Slack as well). Instead, we use it as a file share and central information home. Each group within a team has a channel and we use the tabs to track meeting notes, embed external…

> we use it for file sharing File sharing: apparently still a problem almost four _decades_ after the Internet was invented.

sharing information while controlling who gets to see it, who does not, making sure it is timely, making sure it is gone when it is no longer timely, and making sure all of these things continue to be the case is still a problem more than six _centuries_ after the invention of the printing press.

Re: The Horror of Microsoft Teams

#107
post #65

Earlier quoted context omitted.

> self host ... totally free Self hosting stuff is work for someone, and either needs hardware or rented VMs - it's the opposite of "totally free". This is why this happens.

Not to mention the engineering hours spent managing it.

My experience with these things on AWS is that they are pretty much set up and forget.

Re: The Horror of Microsoft Teams

#108

Earlier quoted context omitted.

> That being said, the Teams UX will slowly and steadily improve. That's not the Microsoft way. It'll accumulate features without ever deprecating bad features, not fundamentally improve. Look at Outlook. That terrible threading has its roots there. There'll be _someone_ out there who loves it, so it'll never go away.

They've changed. Now they routinely redesign stuff. Add stuff that no one wants and cripple or remove those they want. And then make it slower. Outlook web is a perfect example. It's 10x slower since the last redesign and their exclusive killer feature - SWEEP no longer works for me.

Have you sent feedback?

Re: The Horror of Microsoft Teams

#109

Earlier quoted context omitted.

How big is your company? Have you tried the search 'feature'?

I’d say about 200 people IT team. Our company culture is not very tightly interested with each other so may be there is less chatter around the company channels. At this point its email tool in chat format. I personally love it.

Have you tried any other chat system?

Re: The Horror of Microsoft Teams

#110
post #66

Microsoft ruins Skype, then tries making their own communication tool. Ugh. What is it again that Microsoft is getting such accolades for? Visual Studio Code is fantastic. Github is great, but they bought that. Office 365? OneDrive? I'll give you those. Hosted Exchange is a thorn in my side. Internet Explorer and Edge are (were?) both a joke. I don't have any experience with Azure. Xbox is great. Their server product…

> Microsoft ruins Skype, then tries making their own communication tool. Even some rumors MS is in the market to buy Zoom.

To be honest, that sounds like the perfect fit. It already feels much like a MS program.
Post reply on HN