GitHub staff are required to use Teams by Sep 1, 2023
171–180 of 725 posts
Re: GitHub staff are required to use Teams by Sep 1, 2023
#172Re: GitHub staff are required to use Teams by Sep 1, 2023
#173Earlier quoted context omitted.
Because it's by far the worst UX-wise. If you know better tools, it's just shit. To add insult to injury, it kind of sort of works, sometimes, but there are tons of small problems here and there all the time in many cases. I had to use it only for video calls for 3 years, and probably weekly there was something wrong like restart needed because it screwed up my audio.
> Because it's by far the worst laughs in WebEx
Teams has the worst layouts for the videos, moves UI elements to inconvenient places, often has more stuttering…
WebEx is clunky but far superior at what it’s meant to do.
Re: GitHub staff are required to use Teams by Sep 1, 2023
#174Somewhat ironic that a company that’s entire existence was based on the idea of giving developers great tools no longer values giving its own developers great tools. Only a matter of time before this new attitude towards developers shows up in the product.
My Teams works fine on my Mac without issues. Have been using it for over a year now. Fwiw - I don’t understand why it’s hated. It’s a collaboration tool - mainly messaging and conferencing. It’s been decent at that for me.
Re: GitHub staff are required to use Teams by Sep 1, 2023
#175Earlier quoted context omitted.
It's like "leave when the free soda disappears" - people who have "been around long enough" learn to notice the signs that tell them it might be time to start looking. Others (and this is entirely valid in my opinion) see and notice and decide to ride it down all the way to the ground; this can be valuable also as a dying company is likely to promote anyone who remains; title inflation is a real thing. Or another way…
I'd love to hear more about these "leave when the free soda disappears" signs. I think a lot of us can benefit from the unmoderated experiences of others who've been in this situation. When "lifers" start disappearing that's a big indicator the show's over.
Note that it doesn't even have to be malicious at all; it's just a sign that the company is switching from the company you started working at to something else. Not everyone is up for that kind of change. Imagine the difference between working at the plucky startup trying to do X and working at any of the huge companies those startups can become.
Re: GitHub staff are required to use Teams by Sep 1, 2023
#176Re: GitHub staff are required to use Teams by Sep 1, 2023
#177How is it possible that Teams is still such a poor product? I really didn't like it when my job switched like 6 years ago, and I don't recall ever feeling that it improved in any meaningful way. I switched jobs to one using Slack and it's not perfect but it is a lot better. It's almost a meme at this point. In the presence of other clients that have gotten it "right" (or at least more "right" than teams) like Slack,…
> How is it possible that Teams is still such a poor product? List of products Microsoft makes: - [bajillion item list of everything including the kitchen sink] List of products Slack makes: - Slack Microsoft gives Teams away for free and to them it's worthless. They have no incentive to make it great, just good enough that you'll look at the price of Slack, look at the price of Office 365, and say "ehh, we can save…
That's not true, I would switch to Office 365 if it didn't suck. Having an entire suite fully integrated and under one license is a great value proposition - but the thing has to work. I've had to use Teams over the years and every time I get the same shitty experience I've had with it 5 years ago when I first tried it.
Re: GitHub staff are required to use Teams by Sep 1, 2023
#178Somewhat ironic that a company that’s entire existence was based on the idea of giving developers great tools no longer values giving its own developers great tools. Only a matter of time before this new attitude towards developers shows up in the product.
That's overtly harsh take I think. Teams has issues; but asking employees of a company to use said companies tools internally isn't necessarily a bad thing. Hard to improve without dogfooding.
Issues like unable to switch teams without re-authenticating? Slack can do this, Discord can do this, both of them completely seamlessly but Teams just can't.