Teams is so horrific we banned it. If you force us to use teams you'll have to find another supplier. Seriously, it is incomprehensible that Microsoft would ship something so utterly broken. I know they don't have a reputation for writing good software but Teams is on another level, and I don't mean that in a positive way. I've really tried to get it to work but it is so messed up that I don't think it can be done. M…
GitHub staff are required to use Teams by Sep 1, 2023
461–470 of 725 posts
Re: GitHub staff are required to use Teams by Sep 1, 2023
#462Re: GitHub staff are required to use Teams by Sep 1, 2023
#463Earlier quoted context omitted.
Background noise cancellation is pretty bad compared to zoom. Teams seems to flake out more when sharing desktops than zoom does (though I've had issues with both).
I went from a company that used Google Hangouts, which is like using pen and paper relatively speaking, to trying to use Slack. Slack wasn't official, but it was an allowed form of communication. People who didn't have the vested interested just couldn't figure it out. So while I preferred Slack, having to hold everyone's hands through basic functionality was awful. Now I'm at a place that uses Teams. I don't think T…
When Teams was forced upon us at my company, it was a trash product that I would be ashamed to release. It crashed a lot. It was slow. Background noise cancellation was non-existent. Scroll-back history was nearly impossible. Search was trash. Of these things, it's now more stable and has background noise cancellation, but it's still slower and more difficult to use with garbage search and a confusing interface to find the team you're looking for.
Before we had teams, there was a lot of talk in the company of "breaking down the silos". Well teams has silos built-in. It literally makes it harder to find the right person or team to talk to just by how it's designed.
Re: GitHub staff are required to use Teams by Sep 1, 2023
#464Earlier quoted context omitted.
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 feel like a lot of it comes down to which system & client people use. If you're on PC or macOS and using the desktop client, you're probably having a good experience (as long as you only have one account). If you're on Linux or use the web version, you're probably going to have a bad time.
My biggest complaint is missing notifications when the client is not focused. I can't imagine how a top tech company can create a chat client that doesn't fetch notifications when running in the background.
Re: GitHub staff are required to use Teams by Sep 1, 2023
#465Earlier quoted context omitted.
Broken means "doesn't work". I've used Teams for 2 years now for conferencing, chat, desktop sharing, etc. It works just fine. I think a lot of Microsoft hate is clouding judgement here. People want Teams to suck.
I simply can not get it to work. Note that we are on Linux/Chromebooks depending on the person in the team and this alone seems to be a major barrier for something that should be a non-issue. Every two bit video chat site in the world seems to have this figured out.
Re: GitHub staff are required to use Teams by Sep 1, 2023
#466Teams is so horrific we banned it. If you force us to use teams you'll have to find another supplier. Seriously, it is incomprehensible that Microsoft would ship something so utterly broken. I know they don't have a reputation for writing good software but Teams is on another level, and I don't mean that in a positive way. I've really tried to get it to work but it is so messed up that I don't think it can be done. M…
Not only that, every time I've gotten a Teams link for an interview, the desktop app tells me "this version is only for organizations" then the webapp refuses to load.
A huge pain when every other client I've used (Discord, Webex, Zoom, Google Meet) works with minor tinkering.
Re: GitHub staff are required to use Teams by Sep 1, 2023
#467Regardless 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…
Not really I think, considering that MS bought GitHub, with all of its already existing culture. I see this move as them homogenizing the infrastructure. And also not willing to pay to another company for a product that's actually their competition.
Re: GitHub staff are required to use Teams by Sep 1, 2023
#468Re: GitHub staff are required to use Teams by Sep 1, 2023
#469Slack and Teams have this really bad idea of hiding all messages in threads and having the users click around to find them from threads.
Has any tool copied Flowdock's threading implementation? They got it right.
Re: GitHub staff are required to use Teams by Sep 1, 2023
#470Earlier 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 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…