Live data from Hacker News

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

twitter.com

631–640 of 725 posts

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

#632

To 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 c…

L9s ship more ppt than code

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

#633

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…

Teams makes no sense. The audio on it is objectively terrible for calls. Zoom is crystal clear [Its UI has issues though] but on teams I have to actually move my head closer to the computer speakers. Another interesting aspect of it is that it appears actually limit the volume. I plug in better speakers during a call and no change. On zoom it just auto sense the new speakers and boom louder.

I don't understand why teams constantly asks me if I want to upload a new version of a document when I upload a document, the answer is always yes, that's why I am uploading it. I dont care what you do with the original. I am sure there is a way to fix this but I don't have the energy to figure it out, I just want it to work like slack. Why does it have a separate notification area for people using emojis that makes me click outside of the chat to remove the notification?

The entire thing is so far removed from intuitive and "it just works" that I almost think its intentional.

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

#634
post #541

Earlier quoted context omitted.

> In big companies like GitHub people don't typically choose their own video conference platform. It's picked for them. Yes, for larger meetings that applies. Realistically, people will ping each other and video call on slack/hangouts/whatever if they don't like company's choice.

In my Big Company (400,000+ employees) it is not permitted to use other systems to host meeting without authorization. Using unapproved software is strictly not allowed. There can be plenty of reasons including business data security, legal data retention, international data privacy laws, licensing agreements, etc. I remember when Skype was considered controversial because indication of working status and access to e…

400,000+? I don't mean to question this but that's a crazy high number assuming it's not Amazon or Walmart.

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

#635
post #184

Earlier quoted context omitted.

I've been using it on Windows for well over a year. I can't speak to how well it works on Mac or Linux, could be a terrible experience, I dunno. In my opinion, its not the most ergonomic tool out there but its by far the most fully realized tool out there. There's lots of tools that are good for this or good for that, but mixing them in together gets to be a bit kludgy. Having calendars, live editing of documents, me…

> like the threaded messaging, kind of a mess, maybe we just don't do it right I haven't found any chat style application that does threaded messaging "right" with how I think it should work (I want real time USNET with thread level ACLs). That said, they're all ok IF (and that's a big if) everyone working with the accepts the "this is how they work" and use it as such with the appropriate level of technical literacy…

I do agree, threaded chat seems challenging. I feel like I most liked Mattermost's setup where everything that was a reply to can be opened up side by side with the existing chat. Nothing is hidden by being in a separate thread, its obvious when something is a reply to, you can also just jump to the last reply to in order to get more context, etc. Obviously, tradeoffs with every style. Speech is messy no matter the medium it seems and everyone has their own yum.

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

#636
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.

You should try searching for a message in teams, and then finding the context (not just one message before/after) of the message.

It just doesn't do that lol.

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

#637
post #634
post #541

Earlier quoted context omitted.

In my Big Company (400,000+ employees) it is not permitted to use other systems to host meeting without authorization. Using unapproved software is strictly not allowed. There can be plenty of reasons including business data security, legal data retention, international data privacy laws, licensing agreements, etc. I remember when Skype was considered controversial because indication of working status and access to e…

400,000+? I don't mean to question this but that's a crazy high number assuming it's not Amazon or Walmart.

At a guess there's at least 20 companies with head counts that high, and most of them aren't tech and retail.

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

#638

Earlier quoted context omitted.

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,…

I have to ask: what the hell is wrong with your perception? What other IM/AV applications have you used before, and on what hardware? If you've never seen better, it's not surprising that you'd think Teams is good. I vividly remember that 20 years ago there was MSN Messenger, and the experience was far better than that of Teams on hardware at least an order of magnitude less powerful. After that was (pre-MS) Skype, w…

Really? I use zoom for hours and it regularly eats my PC.

If teams works just barely there is something wrong with your setup. None of the chat/im applications work barely. They work, to a point, then crash/glitch/etc.

Let’s see, Slack IM notifications on mobile are garbage, I’m just going to assume that I will miss them at this point. Slack audio is an actual joke, we redirect it to teams…

Zoom, eats our computers. We screen share 3-4 hours someone’s screen will turn black because the video card driver will crash, daily.

Google, does mostly ok for calls without sharing and one person speaking. Limited support for physical devices, calls, etc. noise suppression is minimal so having more than one person unmuted is going to blow an ear drum. Limited features.

GoTo, as long as you are using it as a phone and not an app, you can make a call hurray!

Webex is crap end to end, but you will join a session and get through a call, mostly without blowing up. Feature rich? No.

Teams, let’s see random client gui crashes, but the call stays up so you can keep talking but can’t do anything? Probably weekly occurrence on the current release. Sensitive to https termination in networks and offload, oh hell yes. Forgets camera mappings just like slack every time? Yes and yes. Continues ringing on your phone if you pickup on desktop. Yes just like zoom, but at least it can transfer to desktop, most of the time.

I use all of them, for clients, daily, weekly, monthly. Teams by far is the most feature rich client. Somewhere in the middle of consistency, stability, etc.

Is it magical and poops unicorns? No but ya’ll need to stop being dramatic. They all work, mostly, some have cool features, some are dead in the water like slack, WebEx, GoTo, etc. MS is dumping tons of money into developing teams, they are going to break a lot of eggs, less than in 2020 but still enough to make a mess.

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

#639
post #11

Somewhat 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.

Well considering opening my start menu can lag depending on the internet connection, I would say it already has.

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

#640
post #196

To 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.

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.

Did Google chat decide the reverse the scrolling of one of the chat tabs without notice so everyone wasted a day scrolling down to get to the latest message only to find they were going to older messages.

But they didn't reverse the other tab, so depending on context you may need to scroll up or down. What a crappy UX which still occasionally catches me out.

Teams also wants you to create a "team" for a group chat, but this also creates a sharepoint site and other pointless tabs for documents to go in. Now you have probably just lost discoverability of requirements.

I've used Google chat and it was a pretty rubbish chat. However Teams is not just bad software, it's user hostile.

Post reply on HN