GitHub staff are required to use Teams by Sep 1, 2023 • Hacker News Board

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

#721

Post by hnbad » Thu, Feb 16, 2023, 9:51 AM UTC

generalk wrote: post #483

npteljes wrote: post #467

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

Given how human psychology works, Occam's razor would suggest the most likely explanation is "it's not sufficiently better to overcome the inertia of everyone already being accustomed to what they're using".

HN of all places should know better than to believe that people using one thing instead of another must mean the other thing is worse.

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

#722

Post by FridgeSeal » Thu, Feb 16, 2023, 9:59 PM UTC

waste_monk wrote: post #529

generalk wrote: post #483

Earlier quoted context omitted.

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

In my previous workplaces I have used primarily Slack, with teams for larger video calls.

In my current work, it’s 100% teams. I’d be doing in my heels over swapping to teams as well if I was GitHub, using it for any kind of text communication is such a massive downgrade.

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

#723

Post by raffraffraff » Sun, Feb 19, 2023, 11:34 AM UTC

raffraffraff wrote: post #648

samiru wrote: post #196

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

Multi-line code blocks are impossible on the Linux client. And Android (just confirmed). I have to use this feature about 10 times a day and triple backticks works about 1% of the time so you know what i do? I copy a multi-line code block from another chat and edit the text. Garbage. I can add a code snippet but that thing is bloody awful. What's with the huge title over the snippet and truncating the text to a few l…

For anyone finding this, code blocks do work. But unlike every other editor I've ever used, it's not three backticks that activate it. It's three backticks and a space.

Why in hell would I think of adding unwanted whitespace after the backticks? Anyways, that's the fix.

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

#724

Post by lovecastro » Thu, Feb 23, 2023, 9:29 PM UTC

mullingitover wrote: post #155

kimbernator wrote: post #72

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

In what ways does Teams "suck?" Slack is wildly more expensive, so it's hard for people to see the value in paying so much for it. How does Teams negatively impact the bottom line for a company?

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

#725

Post by ryanbliss » Mon, Feb 27, 2023, 11:11 PM UTC

wkat4242 wrote: post #579

generalk wrote: post #421

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…

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…

Pro tip: go to settings. In general, there is a "Chat density" setting. Change that to "Compact". Wish this was the default because it is so much better!