Live data from Hacker News

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

twitter.com

201–210 of 725 posts

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

#201
post #7

No surprise here, but I wish almost anyone else purchased github instead of Microsoft. One can hope the founders will eventually pull a "MySQL" --> "mariadb" :) I wonder when github developers will be forced to moved from Linux to Windows ?

Microsoft employee here. I was actually handed a MacBook Pro on day 1, I didn't even ask for it my manager at the time just assumed. There is a large community inside Microsoft using Linux as their daily driver.

Yup. I was given a Surface Book and a MacBook Pro when I joined Microsoft in 2017, and the Surface Book was just so I could do some testing for things in Azure and make sure it worked well-enough on Windows. My last year at Microsoft, I focused entirely on Linux and used a combination of devices and there was even an internal team focused on making it possible to use Linux as your daily driver with little impact.

At GitHub (where I work now), it’s standard-issue MacBook Pros.

A lot of teams at Microsoft even used Slack internally before 2020. Compliance issues (and I’m sure cost) forced us onto Teams, which was unfortunate, but as a company, Microsoft was a lot more free/open than most other companies of its size with regards to what tools teams and individuals could use — especially when it comes to what you have to do to your own machines if you want to bring your own device to work (the InTune policies are completely and totally sane, more sane than when I worked for a company owned by Univision and Univision wanted me to call the help desk anytime I needed admin access or to install something outside of the Mac App Store — things I frequently needed to do for my job).

GitHub has completely separate IT systems. I can’t/won’t comment on what changes are happening for video calls, but I don’t see this as some sky is falling moment.

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

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

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.

If you use it for a single company (ie one login) it is OK, but IMO a worse experience than Slack; MS get away with it because it is free.

Where the true nightmare begins is when you need to login to multiple tenants/workspaces. You simply can't use multiple at the same time, and switching from one to the other is super slow and unreliable. I tried to do so today and Teams crashed 4 times, at which point I uninstalled it and decided to just use the web app instead.

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

#203
post #154
post #37

What's the problem with "4 yr old laptops"? My colleagues and I use Teams on computers 1-5 years old and haven't heard about any issues.

> Teams on computers 1-5 years old and haven't heard about any issues. My 2019 Intel MacBook would sound like a jet engine taking off when opening IntelliJ. Apple’s M2? Doesn’t even get hot doing a full index and battery lasts 4-5x as long. The quality of life using an Apple Silicone laptop while traveling is so much better. Frankly, it’s an embarrassment for Intel.

Silicone is a polymer of siloxane which makes rubber-like substance such as silicone oil, silicone grease, or silicone caulk.

Silicon is an element often used in semiconductor manufacturing.

Neither Apple or Intel manufacture silicone in any major quantities.

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

#204
post #50
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.

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.

> Hard to improve without dogfooding

They've been dogfooding and I don't think most of us regular users have seen any measurable improvement for years. Apparently it's hard to improve with dogfooding too?

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

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

I am forced to use Teams on a Mac. It's beyond horrible. Messages sometimes take an hour+ to appear.

I would crawl through broken glass for google chat. Teams is sooooo bad.

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

#206

One thing to keep in mind is that there's a security angle to this as well. It is beneficial for a company to centralize all of its communication through one service which can be audited for security and also support all the features required to meet the internal Requirements. Having multiple tools multiplies the work needed to maintain security standards. Of course, I'm not saying that teams is more secure than comp…

They aren’t centralizing their communication in teams. It’s being used for video conferencing. Everything else remains in slack.

Read the image in the tweet, it’s only 100 words or so

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

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

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.

It has not been decent for me.

Here is a specific complaint about messaging. If you want a tool for programmers to collaborate, don't have it automatically insert smart quotes when trying to quote code in messages.

You have to search to figure out how to turn it off. And if you do, it will still turn that back on sometimes for no particularly good reason. And my being able to send them correctly doesn't help when someone else posts code and it gets converted on THEIR end.

Yes, yes. You can just attach a file. But it is a collaboration speed bump telling people that they have to save snippets to a file, then share the file, rather than simply using cut and paste in the obvious way. Doubly so if you're interacting asynchronously and you're reading their message some time after they mangled it.

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

#208

Earlier quoted context omitted.

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.

For people who are not solely at one company - contractors/freelancers who perhaps need to support connectivity with multiple organizations - MS Teams is a huge hostile pita. I had 2 clients each using Teams, and I was working with each. But... I can't just be 'logged in' to two different Teams organizations. If I was in company A, I couldn't see anything from company B. Apparently you can do this in the phone app, b…

also the way it collapses long unread threads so you can only see the last couple messages, then marks the whole thread as read when you view those

I missed messages and conversations all the time when I had to use it

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

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

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 has been awful.

The platform is slow, and every time I have to use it, it feels completely obtuse in unique and frustrating ways. After nearly three years of weekly interactions, I regularly am confused by what I am meant to do, or how to resolve errors that occur; it is the single most frustrating online tool I have had to use, largely because the decision to use it is out of my hands.

The absolutely sole saving grace for the tool is that I can now effectively use it with a web browser, instead of the invasive thick client application that I was required to when it was first rolled out.

If my employer required me to use it, I would immediately find another job. It's that bad.

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

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

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.

I find Teams to be just fine for instant messaging and conference calls. It's everything else that is awful. I hate the way it has files stored in a "Team" almost as much as SharePoint. I can never find what I'm looking for and ultimately have to ask and then create a browser favorite to every doc for $current_project.
Post reply on HN