Live data from Hacker News

GitHub staff are required to use Teams by Sep 1, 2023

twitter.com

571–580 of 725 posts

Re: GitHub staff are required to use Teams by Sep 1, 2023

#571
post #536

Earlier quoted context omitted.

> The platform is slow > I regularly am confused by what I am meant to do, or how to resolve errors that occur; Just to provide two examples of specific complaints from the parent post.

Have the same experience: - ms teams on my windows laptop turns it into a raging heater. While i dont even have my webcam on. - ms teams is so multi-functional you can do anything with it. Office suite, create polls (that are very laggy). It is so bloated there’s clearly no straightforward UX flows. Buttons all over the place. Desktop UI feels terribly slow. - typing in chat boxes is laggy as hell. I’m not alone. My…

My complaint? Well, back when I had to use it (between jobs now), I found the app (Mac M1-base laptop) to be slow and painful to use. But using Teams via a website? Way faster, which I found odd because I think both are web based (I think the "app" just contains its own instance of Chrome).

Re: GitHub staff are required to use Teams by Sep 1, 2023

#572
post #196

Earlier quoted context omitted.

I wonder if those who complain about Teams actually use it. They might not. My company forces us to use Google Chat. I would take Teams any day.

> My company forces us to use Google Chat. I would take Teams any day. For video or text chat or both? Meet + Slack is my preferred solution. IMO Google Meet is the easiest to use video meeting software. Click link and the person is dropped in the meeting. Slack is the best text chat. Zoom is fine. Teams is a dumpster fire on my mac. I have a couple external meetings that are Teams and I have to remember start trying…

Have you tried using it via a web browser? https://teams.microsoft.com (If I recall correctly---it's been several months since I've had to use it). I found it worked much faster than the actual Mac app.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#573

Regardless of what you think of Teams -- I myself have had nothing but poor experiences over 2.5 years of using it daily -- it's telling that Microsoft has to require folks to use Teams. I'm sure this is just Microsoft unifying everyone on the same comms platform, but seriously, I don't know anyone who chooses Teams. I know non-tech folks who chose Outlook 365 because of familiarity and then end up on Teams because i…

I remember the first 1-2 years after the iPhone was released, I see Microsoft employees (I mostly see sales and presales folks) using their iPhones under the table or when the meeting attendees from other companies aren't around. Heard they were supposed to use them.

Says something.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#574
I had to sign into teams for a job interview.

It took me half an hour to get it installed and signed in. Most of that was trying to sign in. I think to a required Microsoft account. Who has a "Microsoft account"? I couldn't just use an email address. There had to be a Microsoft account tied to it. Or something.

To me, it's a red flag if a company uses MS teams.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#575
post #220
post #196

Earlier quoted context omitted.

I wonder if those who complain about Teams actually use it. They might not. My company forces us to use Google Chat. I would take Teams any day.

I use it and I would be happy if Teams was able to do basic copy/paste. When you copy, it copies things you didn’t select and doesn’t copy some things you selected. When pasting, it auto-formats the text and does a terrible job at it. It’s a disaster. I hope the Teams team is forced to use Teams.

My favorite: when you use dark mode and the person on the other side the default light theme, text that you write will appear black on their screen and white on yours (so far so good). Now if you copy & paste text that they have written, it will appear white to you and white to them, making it impossible for them to see.

Just crap.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#576
post #491

Earlier quoted context omitted.

On a regular basis I use Teams, Zoom, and Jitsi for video conferencing. Teams isn't the most troublesome of the set. > I'm sure this is just Microsoft unifying everyone on the same comms platform, but seriously, I don't know anyone who chooses Teams. In big companies like GitHub people don't typically choose their own video conference platform. It's picked for them. For Microsoft I can see a huge benefit to using Tea…

Curious now, which one would you say is the most troublesome in your experience out of those three then? And why…

Not the OP, but Jitsi is terrible.

For me, ranked:

Zoom

Google Meet

Discord

Slack

Teams

Anything else

Re: GitHub staff are required to use Teams by Sep 1, 2023

#577
post #209

Earlier quoted context omitted.

I will be blunt. Teams is an awful user experience; I have been using online collaboration tools since the BBS days, and while I appreciate and understand why and what they are trying to build, it is bad software. Every single experience I have had as a teams user in professional settings, interacting with communities, and being required to use it for interactions with my childrens schools since the 2020 shutdowns ha…

I simply don't understand this at all. I've used in 3 of my last workplaces. Two exclusively and one in addition to slack. No particular complaints for having internal meetings of any size. I literally do not know what you are talking about and feel like I am missing something.

I'm with you - I don't love teams, but it's certainly no worse than Skype. We use it constantly for meetings, chat and calls in our team of ~20, and across the broader organisation. There were some teething problems when it was first rolled out, but I think that was mostly our infra guys getting things configured correctly.

Our dev team uses Slack for chat, but that's only because we can't connected to the corporate Teams from our dev environment.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#578

Earlier quoted context omitted.

I am starting to fear that I am missing out on something major, because we've used Teams for years now and it works fine (on macOS) for what we do - basic chat, multiplayer powerpoint, some video calling, etc. Maybe it's a team size thing, and Teams just blows monkey chunks when you're one of fifty thousand employees at a company?

It’s been a year since I’ve used teams but my biggest gripe is search. Conversations are contextual. My work often requires me to find conversations that happens months ago. When unused Skype I could god into my email and recover it that way. With teams , back when I used it, you could search no problem. What you couldn’t do is go back to a conversation and get the context. I’m not sure how on earth you ship a search…

To add copy and pasting conversations more than one page doesnt work and there is no feature to export conversation.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#579

Regardless of what you think of Teams -- I myself have had nothing but poor experiences over 2.5 years of using it daily -- it's telling that Microsoft has to require folks to use Teams. I'm sure this is just Microsoft unifying everyone on the same comms platform, but seriously, I don't know anyone who chooses Teams. I know non-tech folks who chose Outlook 365 because of familiarity and then end up on Teams because i…

I think the biggest problem with Teams is the leadership's strategy.

They seem to be focusing on adding as many glossy features as quickly as possible. The quality, performance and consistency doesn't seem to be a point of consideration at all. Yet for a user who spends a lot of time in it each day, I really don't care about animated waves on top of my video, or this together mode. I just want it to work and not take ages to open, show stale status info until I click on a user, have choppy video, running my mac's fans on full blast, and be so cluttery that it's almost impossible to find back information we shared in chats in the past. And the worst thing for me: the information density is so low. These big bubbles around everything seem to care more about looking pretty than to actually show information and cause way too much scrolling. Slack does this so much better.

The Teams guys can learn so much from their VS Code colleagues. It's really weird how one company can produce one of the worst infamous electron apps and also the gold standard best one at the same time.

Ps and please, tell me what's going wrong. "Something went wrong" is ridiculous. And let me log into multiple tenants at the same time without switching.

Re: GitHub staff are required to use Teams by Sep 1, 2023

#580
post #149

Earlier quoted context omitted.

They are still using Slack. This is for video conferencing only. I've heard that with regards to video conferencing, it's competitive with zoom.

> I've heard that with regards to video conferencing, it's competitive with zoom. Did you hear that from a Microsoft salesperson? Only a person who hasn't used both regularly can say that. UX and features on Zoom are better. The mere fact that to this day Teams has wildly different features depending on how you join the call is a joke - for instance, joining from a browser on macOS results in no chat (the button simp…

>(the button simply isn't there).

What?! This has to be a glitch or something. How can something so basic be simply missing this long? Teams is not a new product. I just checked. It's 5 years old.

Post reply on HN