Live data from Hacker News

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

twitter.com

521–530 of 725 posts

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

#521
post #486

Earlier quoted context omitted.

>it's telling that Microsoft has to require folks to use Teams. 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.

> not willing to pay to another company for a product that's actually their competition. This. Companies are cutting costs. Teams may not be the best to use, but it doesn't make sense to have multiple chat solutions.

Hmm, GitHub has a gran total 2100 employees.

Even if they were paying 10$ per user, it's basically the salary of one non-lower level engineer to have cross-company communication they are already used to.

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

#523
Teams for sure is a worse experience than slack. Why Microsoft chose to separate teams and chats in the UI is one of the biggest wastes of time each day. Several seconds to switch between them. Arg... Wish someone had a more viable FedRAMP compliant competitor to office365.

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

#524

Earlier quoted context omitted.

>Making Teams not suck doesn't move their revenue dial one iota. 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.

> I would switch to Office 365 if it didn't suck. From what? O365 collaboration is terrible. If you do joint document editing, O365 will drive you nuts after using something GSuite. What many do is have GSuite and then O365 for people who need office products for various reasons.

I don't quite know what I'm doing right but half my day is spent in Teams and the other half is in documents with 4-6 other people working in them at the same time and I can't remember the last time we had a real issue.

I can understand Teams being a pain in multi-tenancy setups but even that is something which I've noticed is being improved recently.

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

#525

Earlier 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?

For me the ability to seamlessly start a meeting, pull in 10 participants from different organizations by just sharing a URL and be off to the races a few minutes later is what makes the difference. If I have to spend even a couple of minutes debugging audio/video issues, dealing with people that can't seem to join, people that are trying to install a client that they then can't get to work, people that need to make…

The fact that there's almost never a dialin for Teams meetings makes me hate it. I want to be able to dial in with my desk phone.

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

#526
Having read a number of GitHub incident reviews I'm really curious how this will impact ChatOps. They're one of the first companies I saw that seemed to use ChatOps for almost everything, including things like updating BGP routing. Do they have 7 months to migrate everything to Teams or will they keep some Slack workspaces around just for ChatOps?

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

#528
post #438
post #374

Earlier quoted context omitted.

>"I know they don't have a reputation for writing good software" I think they have a problem that regular person supposed to hate MS and Windows. I also think MS is quite capable of and does produce good software be it their own OS, Visual Studio, Visual Studio Code, Word, Excel, Flight Simulator etc. etc.

> I also think MS is quite capable of and does produce good software be it their own OS, Visual Studio, Visual Studio Code, Word, Excel, Flight Simulator etc. etc. All i can say: good luck using it. I did not have, any.

Been using it forever. No problems except skipping some windows versions like Vista and Win 8.

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

#529

Earlier quoted context omitted.

>it's telling that Microsoft has to require folks to use Teams. 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.

Of course, and I can't fault Microsoft for that, even if (having been on the bad end of a similar acquisition and IT merge) it sucks for GitHub. My point was: GitHub as an organization didn't choose Teams willingly, and are still paying for Slack and only using Teams for video conferencing. Of all the explanations of why that might be, the easiest to land on is "because Teams just isn't that good."

Or it could just be that "this is the way we've always done it" / that Slack has enough inertia in the organisation that changing workflow, updating shortcuts, etc. is inconvenient and thus left until the last minute to change over.

I haven't used slack but broadly speaking Teams / Zoom / all of the other platforms I've used have been roughly the same, in that they all get the job of text and (usually) video communications done. Some might be a bit nicer to use than others but largely it doesn't matter which one you use as long as everyone is on the same platform.

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

#530
post #144
post #50

Earlier quoted context omitted.

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.

"Teams has issues" is an understatement, the app will sometimes notify you that you have a new message, and when you try to open it from the web page, it won't show up, but if you force refresh it will. Or it will show up on the mobile client, but not on the web one.

The default settings give you a notification in the notifications list when you get a thumb's up in the chat you're currently reading. You'll have to switch views to clear that notification(!) beyond infuriating for such a small thing.
Post reply on HN