I guess my comment is against the grain. But I do enjoy Teams. More over, I (as consultant) moved three orgs onto Teams and the clients are happy. Its fantastic integration and communication platform. Enjoy!
GitHub staff are required to use Teams by Sep 1, 2023
611–620 of 725 posts
Re: GitHub staff are required to use Teams by Sep 1, 2023
#612Regardless 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…
Can you imagine the morale of an engineer/designer known for working on the worst-in-class product?
Re: GitHub staff are required to use Teams by Sep 1, 2023
#613It is a pretty clear sign your product has failed when you need to _force_ one of your biggest acquisitions to use it.
Re: GitHub staff are required to use Teams by Sep 1, 2023
#614Earlier quoted context omitted.
What does it mean to be worst-in-class for text chat or video conferencing. Video conferences look and sound great. Text chat is text chat. What am I missing here that's so awful?
Teams regularly randomly gets worse in many metrics. I will start work one day and something will randomly work differently, with no warning. One good example is that teams now tries harder to autoformat code. It will refuse to treat something copied from an IDE as just text, automatically put it into some random quote style box, and the process of getting your cursor out of that box to continue writing your message…
Pasting code in teams requires 4 clicks and there is no keyboard shortcut. How is this expected to be used by developers is beyond me.
Also try to right click on an open image and click copy. Then paste in another application (even a Microsoft one). Comes out as a base64 string. This been broken for years.
Re: GitHub staff are required to use Teams by Sep 1, 2023
#615Regardless 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…
It's boring reading comments like these. Really? 2.5 years of " nothing but poor experiences"? I have to ask: what the hell is wrong with your computer? I started using Teams heavily in 2020 and yes, back then it was unequivocally the worst of the bunch. But I've seen it make great strides, and it's been many months, perhaps years since I've really had any problems with it. Audio, video, screen sharing, PSTN dial-in,…
Umm, teams video will reliably cause my surface pro 7 to actually BSOD. Not exaggerating, having the video turned on will cause a no-shit BSOD on Microsoft hardware, and my coworker with the another surface also has that issue.
On my desktop with a no-name webcam with a generic driver I have no issues with teams, but the complaints about the software are rooted in actual problems. It's inconsistent, I've never seen a program that can have so many different bugs. We have 2 users who regularly use teams to communicate with an external vendor, they are on exactly identical Dell desktops. One has no issue at all, the other will see massive performance issues when teams is running in the background, somehow it is saturating disk read on a ssd. It would be hard to have more identical systems, they are running the same OS image with the same programs installed, the only thing that's different is the user account they are signed into. I finally just gave up and swapped the user's entire system with a spare, which resolved the issue but as far as I can tell there are no problems with that system. I pulled it out of spares 2 months ago for a new employee and they have not reported any issues at all, and I have followed up with them out of curiosity.
Teams is just super inconsistent, so the fact that it works on 1 computer for you doesn't in any way invalidate all the other problems people report with it.
Edit: unfortunate autocorrect typo substituting a slur for the worn 'new'
Re: GitHub staff are required to use Teams by Sep 1, 2023
#616Regardless 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…
Fwiw, I do know quite a few companies outside the tech space that use, and even love teams. These are the ones where I have personally gotten to see how they use teams:
2 car sale companies. 1 Accounting shop. 1 ultra large company that owns multiple types of businesses across 4 different countries. A few real estate businesses. The vast majority of people using it have said they are happy and several have even been excited to show off their setups. All of them said that it allowed them to go remote during the pandemic and has helped them stay flexible once movement and office work started returning to normal.
The way they use it is also interesting. It’s not just chat. They integrate a whole host of apps directly into it including sales pipeline tools, document management, and project management. We are not talking about chat bots either. We are taking integrated apps+interfaces. All their meeting happen in MS teams itself. The multinational has a non trivial arrangements using multiple instances where some are separated for client convos and others are for different teams.
I use the term interesting because the way they use it is nothing like how I’ve ever seen any slack being used. And I don’t think I’ll ever see slack supporting that. Putting it out there because I think there’s a world of use cases for ms teams that doesn’t involve people being forced to use a bad thing.
Re: GitHub staff are required to use Teams by Sep 1, 2023
#617Re: GitHub staff are required to use Teams by Sep 1, 2023
#618Earlier quoted context omitted.
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…
It's CDD, checklist driven development. When you are competing against another product in the enterprise space the people making the decision probably won't be using what you are selling often but they will look at the list of features, so money spent adding new features is more important and higher prioritized than stability reliability or any other nonfunctional requirement.
[flagged]
Re: GitHub staff are required to use Teams by Sep 1, 2023
#619Earlier quoted context omitted.
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…
Opposite experience: I use Teams every single workday and have never experienced the lagginess or laptop heating you describe. I’ve never heard of any coworkers having these issue either. It’s so strange that so many people can have completely different experiences with the same software.
I think it's also the varying differences of experience in using different tools/platforms to communicate. For example, someone coming from Zoom may notice how laggy Teams is compared to Zoom. I definitely felt this way, once I experienced the alternatives to Teams, I just couldn't wait to stop using it.
Why does it need to have excel implemented into it? Why is the search function still there if it literally doesn't do searching. Why does it take 20 seconds to open a PDF?
Many more issues and questions stand out if you've previously used a platform where none of those are issues.
Re: GitHub staff are required to use Teams by Sep 1, 2023
#620To everyone at GitHub: I’m so sorry. I don’t mean this in a clever way, either. Teams is awful and it will make your lives worse to one degree or another.
Is there a single high level engineer (like, whatever L9 is at Google where you make millions of dollars for being a savant) working on Teams? If not, why not? A ton of its problems seem fixable. Discord/WhatsApp and Teams are both Electron apps from what I can tell. Discord/WhatsApp very usable, so it's not like Teams is doomed from the get go without a full rewrite.
Is the entire thing written by a team who don't care/don't know any better/can't do any better?