Live data from Hacker News

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

twitter.com

221–230 of 725 posts

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

#221
post #56

Earlier quoted context omitted.

So the official meetings will be in teams and the important meetings in Slack huddles? Does teams allow you to draw on the screen?

> Does teams allow you to draw on the screen? i mean; no one can really tell you what to do with your sharpie. (but yes; that's been baked in for a while)

Only on a freeze frame of the screen though. Not like in a slack huddle.

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

#222

Earlier quoted context omitted.

Absent a strong business reason otherwise, absolutely. Azure: yes, all the major cloud providers should migrate all of their use to their cloud. If their cloud doesn't support something that's a problem for their users and they need to fix it ASAP. O365: Same thing. VSCode: Developer tools such as IDEs shouldn't be mandated (and weren't when I worked at MS) but if one is mandated it absolutely should be their version…

Besides O365 the rest are not even the same thing. If half your company is on Teams, and half is on Slack, they can’t communicate with each other. Mandating a single communication platform is absolutely the right move. And the fact that MS picked Teams as that single communication platform is beyond obvious. What else could they have chosen?

> Mandating a single communication platform is absolutely the right move

Is it, even if there will be productivity losses? Is making your teams less productive "absolutely the right move"?

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

#223
post #185

I’m extremely picky - as long as my livelihood is not threatened and I actually have options. For me, being forced to use Windows, Teams, Skype, Java/Spring, or Jira (among others) would be a dealbreaker (again, unless that job might be among the few available to help me feed my family). I spent some time learning in the structured environment of a large company, which I recommend everyone do for a first and/or secon…

It's interesting you say this. I've always felt my flexibility was a strength and quite enjoy being asked to use new tools and software. To be honest I tend to look quite poorly on people unwilling to provide flexibility on the tools they work with. In my experience it can be quite disruptive when you have one highly opinionated team member who will refuse to work with a new tool because of a personal preference. I g…

MS Teams is virtually never an engineering decisions it seems. That's not a C# vs Java debate or Visual Studio vs JetBrains - not even comparable. Your argument about flexibly is moot in the context.

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

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

My company uses Teams... and I wouldn't wish it on my worst enemy.

So here's at least one person who is using teams who complains about it.

The shitty UI/UX is one thing, but some of the behaviors are incredibly frustrating. Here's some examples:

- Sharing a single window makes Teams minimize the window with everyones video camera on it into a small window in the corner of your primary screen. I have a 49" wide screen, I can have that Teams window open (so I can see faces/people) and share a window at full-size for everyone else, STOP minimizing that window.

- That small window sits in the bottom right corner of the primary screen, if you move it elsewhere, click on Teams for chat, and then foreground another app, it re-positions itself in the bottom right corner (thereby obscuring whatever app happens to be sitting there)

- All of my meetings that were created through Outlook/Office 365 as a Teams meeting are labeled "untitled" and there is no way for me or anyone else to change the title of the meeting, its worse if the meeting is on a shared calendar

- Teams notifications are the worst, it'll tell me I have 2 messages, but I open the app and there is nothing, OR it's messages I've already seen

- No easy integration for 3rd party chatbots and the like, which is a HUGE thing we use on Slack

- Teams out of all of the apps (including all the security software corporate loves) uses the most energy and power, and is the primary reason that we all upgraded to M1's as fast as possible because then maybe we'd have a chance to use our laptops without carrying the power brick when in meetings

- Tagging people in messages may or may not notify them...

- Meetings allow you to add people to them, but once the meeting is over they get removed from the chat, even if you've tagged those people in the meeting chat with important information, you have to formally invite people to the meeting with the original meeting invite for them to "stick".

- No way to copy/paste entire chat history/print chat history. I have so many screenshots of meetings/notes I need to keep and or share with others.

Overall Teams is one of the worst products I've used, and I was using "Teams" in the Microsoft Lync on macOS during the Office Communicator days.

The lack of native app is a real killer though, and unlike Slack which has done a LOT to improve how they use Electron/how much energy they use, Teams is the slowest and worst of them.

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

#225
post #205

Earlier quoted context omitted.

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.

I'm using a 2017 2.3ghz i5 with 16gbs of ram. I'm in 7 different teams and have over over 15 pinned chats and IM's. The only delay I see is when comparing desktop app to the mobile app. Even video chats are bearable and work fine with even background effects turned on.

So not on a mac then? Because only 1 mac was ever released with an i5, and it wasn't out in 2017.

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

#226
post #91

Earlier quoted context omitted.

Team has issues is the understatement of the year. A simple feature like screen freeze has been requested per use in the thread below hundreds of times... "Between different messaging boards (including the link above) this feature has been requested over 2000 times (1044 times as of this writing on the link above alone). Could Microsoft chime in to let us know if this is going to be on the roadmap? Thanks." https://a…

They don’t even have something as simple as a key combo to mute and other basic functionality (macos).

that's not true. CMD + Shift + M mutes and unmutes your mic. you can also press Option + Space to temporarily unmute yourself.

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

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

Google Chat has improved a lot but it's definitely not there yet from a savvy users standpoint.

I've seen it used with great success at smaller, non-technical companies though.

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

#228
Probably a not so cool answer: It is just a tool, that you will use while working. Not great, better than some other tools out there, maybe not the best tool. Good news: You just have to use it while working. In another hand, I'm thrilled to see which tools the smart people from GitHub will create around it!

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

#229
post #92

Earlier quoted context omitted.

"4 year old laptop" can mean anything from "8 cores, 64 GB RAM, dedicated GPU" to "720p display, 4GB RAM, dual-core". If Github for whatever reason punished its employees with the latter, well. Teams is not the world's most optimized Electron app.

720p, 4GB in 2019?

Yes. Most of the laptops at my current jobs were 720p till 2023. I work for a huge enterprise (over 5k employees).

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

#230

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.

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.

When I first started using teams, I saw the Files capability and thought it would be a pretty useful feature. In practice, the UX completely ruins any benefit of having files integrated into it.
Post reply on HN