Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

twitter.com

Post reply on HN
Print view View original

681–690 of 725 posts

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

#681

Post by watwut »

mfer wrote: post #491
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…

On a regular basis I use Teams, Zoom, and Jitsi for video conferencing. Teams isn't the most troublesome of the set. > I'm sure this is just Microsoft unifying everyone on the same comms platform, but seriously, I don't know anyone who chooses Teams. In big companies like GitHub people don't typically choose their own video conference platform. It's picked for them. For Microsoft I can see a huge benefit to using Tea…

I is not just video conferencing. Teams sux if you need many ad-hoc working groups based on topics or small teams. Meaning, they sux for exactly the kind of work developers do.

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

#682

Post by Spivak »

samiru wrote: post #196
revscat wrote: post #147

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.

The work chat tier list

    Discord
    Slack
    Mattermost
    
    IRC
    Email
    
    Hangouts
    Teams
    
    Linq / Skype For Work
Teams so fundamentally misses what the point of a good office/team oriented chat looks like that it’s worse than useless. They would be better off just splitting off the video calls (which are pretty good but drop the annoying corner thing) and just starting over with a Slack clone.

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

#684

Post by 0xbadcafebee »

analog31 wrote: post #610
0xbadcafebee wrote: post #565

Earlier quoted context omitted.

> it's telling that Microsoft has to require folks to use Teams. Most people, when they get comfortable with something, are averse to change. Even if the thing they would change to is better than what they have , they still won't want to learn a new thing. Not saying that's the case here. But without real data to lead a decision, people just do what they prefer, rather than what's better. (I use both Slack and Teams…

People love change. Look how Google, Amazon, and social media took the world by storm. And pocket calculators, smart phones, large screen TV's, the list goes on. People like changes that benefit them. On the other hand, probably the #1 user request for enterprise software is: Please don't change anything. This tells you something about the software. Common reasons are: * The last major change broke everything and we…

Another way to put it is, people follow the path of least resistance. If they can still make an old thing work, and adopting the new thing seems like a chore, they'll keep the old thing. OTOH, if they see the new thing will greatly ease their life, the path of least resistance is the new thing.

Of course they mostly do this for short-term personal gains. For new solutions that seem like a chore to adopt and only have long-term gains, they won't want to.

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

#685

Post by yurishimo »

Lutger wrote: post #669
kneebonian wrote: post #588

Earlier quoted context omitted.

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.

This resonates. Microsoft does this with a lot (not all) of their products. Its also my experience here in the Netherlands, especially how Microsoft does sales. Its always management who forces everybody to use these products against their will, especially as they come for free in their 365 package. Nevermind that is a pale imitation of an MVP version of their competitor. For the decision makers, it doesn't really ma…

As someone who just moved to The Netherlands, this bugs me as well. Many of my interviews happened over Teams, which should have been red flag. Luckily, my IT department is small enough that we can use Discord for general chat and some video calls, if we don't need high resolution, but we still have to use Teams to interact with the rest of the company.

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

#686

Post by ralmidani »

eterps wrote: post #655
ralmidani wrote: post #401

Earlier quoted context omitted.

I said I’m extremely picky, but the list of things I would be OK using is much longer than the list of things I would not work with unless circumstances forced me to. Maybe I should have also said I’ve learned and/or dabbled in/used Python, Ruby, C, C++, Java, JS (server-side and client-side), CoffeeScript, TypeScript, and Elixir. I currently have a strong preference for working with Elixir (and fortunately that’s wh…

Hi ralmidani, I recognize being picky like that with tech choices. My friend and I are developing a product to enhance the job search process. Especially for devs that want to be very specific on what tech they do and don't prefer to work with. May we ask you a couple of questions? I know you're not searching for a job (kudos on finding an Elixir job) but I think your input would be valuable.

Thanks for reaching out and for your kind words!

I sent you a message on Keybase and requested connecting on LinkedIn. If you’re not active on either, my full name can be found here: https://github.com/ralmidani

Put a dot between the two parts of my name, take out the dash, and send to proton with .me at the end.

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

#687

Post by tstrimple »

ska wrote: post #637
foobaw wrote: post #634

Earlier quoted context omitted.

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.

Was that a guess? It was an impressive one. There seems to be 21 companies with 400k+ people.

https://companiesmarketcap.com/largest-companies-by-number-o...

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

#688

Post by tstrimple »

vxNsr wrote: post #538
epolanski wrote: post #520

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.

I’m trying to understand a world where employees at a large org will install a random comms client instead of just using what’s already installed. I worked at a place that used IBM sametime until they migrated off lotus notes. No one used anything else, because why? You’d need to convince every other person you wanted to talk to use it too, was much easier to just use the existing app.

Often these tools are adopted by smaller teams for their communication. So official company meetings would happen over teams, but bitching at Bob because he still hasn’t reviewed your PR would happen in Slack. It can make information management a nightmare, especially when users start sharing files with each other via Slack.

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

#689

Post by brmgb »

nstart wrote: post #616
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…

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…

Yes, that's how most people use MS Teams. It's extremely useful. The sharing space for documents is good. Collaborative editing in Office is good. Conferencing is good. Presenting from Powerpoint is good.

It's the same thing in every discussion involving Teams: most HN readers don't realise just how unusual the tools they use and what they want are with regards to the average job.

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

#690

Post by hammock »

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…

>there's a difference between "I chose an email/identity platform that I know and I guess I'll use its chat app too" and "I evaluated team chat offerings and Teams is our top pick.”

You literally just described the strategy for every Microsoft software ever. MS Word (vs Word Perfect) comes to mind

Post reply on HN