Live data from Hacker News

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

twitter.com

701–710 of 725 posts

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

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

In my professional life, I have used Webex, Slack, Discord, Skype, and Teams.

I would only pick Teams over Webex and Skype.

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

#702
post #382

Earlier quoted context omitted.

It works mostly fine. It doesn't have the prettiest interface, for example message editing is not great, and search is not great (though it got better than 1 year ago that was unusable). Anther stupid thing is that handling multiple organizations (for example if you are added as external collaborator to another company Teams) is basically broken, you don't receive messages from one if you don't switch to it most of t…

It works mostly fine. It’s also the application I use basically every minute of the day. ‘Mostly fine’ just doesn’t cut it. When we’re talking about an IDE I can just bring my own, but for chat it doesn’t work like that.

Well, fortunately I don't use Teams every minute of my day. When I need it it works mostly fine.

Of course if you use Windows, on other platforms Teams works completely unreliably or doesn't work at all. But that is another issue. I gave up using Linux at work on bare metal and started using a VM (not only for Teams). On macOS it works but not as good as Windows (I have some coworkers that has a mac, they loose notifications a lot)

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

#704

Earlier quoted context omitted.

Shameless plug: that's why we started FossTeams [1]. As most of us are forced to work with this thing, the least we can do is to find a workaround for the problem somehow... [1]: https://github.com/fossteams

Have you considered using official Teams Graph API as your backend layer? https://learn.microsoft.com/en-us/graph/api/resources/teams-...

Yes, and I don't want to follow that because most of the companies restrict third party apps. This means that you can't have a custom client for a good percentage of the companies.

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

#705
post #637

Earlier quoted context omitted.

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

Huh, it was but I can't take credit for being clever about it, just simple order of magnitude estimation with a factor: e.g. I thought of a handful I was pretty sure were 500k+, rounded up to 10, then doubled as I know I don't know much about the space.

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

#706

Earlier quoted context omitted.

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…

Don't forget * The workflow to use your software is so unintuitive I've had to learn it by muscle memory People don't mind when a nice discoverable UI adds some more features. They don't like it when a horrible poorly thought out one that they had to painfully learn is suddenly different. That button that used to be hidden in the edit menu? Now it's on a ribbon menu which has to be expanded. Good luck hunting!

An interesting lesson is to visit a user site and notice the step-by-step instructions, written out and taped to the sides of monitors, or pinned to cubicle walls. Those instructions were often hard-earned, either written by the user or shared among workers. That stuff becomes obsolete if the software changes. Likewise for online instructions, such as blogs that give instructions in the form of screen captures and text, and that are no longer valid. If the unofficial instructions are better than the official ones, or more legible than the GUI, then it's a step backwards for users.

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

#707
post #539

Earlier quoted context omitted.

You’ve mentioned this app before, last I checked there isn’t a usable client yet. Are you just hoping to get more FOSS devs on board or has something changed?

The first one, for now I'm a solo developer on this thing :(

I would love to contribute to this but its way outside my area of expertise.

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

#708
post #673

Earlier quoted context omitted.

If nothing else, Teams is horrendously inconsistent and one might naïvely think that MS would want to dogfood it better, with good statistics. This HN article now has nearly 600 comments of people – mostly – griping about Teams. A large number of them are replied to with people saying "Oh, it's never done that for me!" or, alternatively, "Teams never works fully, but at least X works" being replied to by "X has liter…

Exactly, thank you so much for putting the experience into words. The random errors are just so... astoundingly random. I've had problems with a headset on USB-C (Sennheiser EPOS). Teams would connect once, and then never again. Another time it would stop responding to any click. Then it would reload whenever changing team/channel. And then it would no longer show any notifications. I haven't seen an app with that am…

Yah Bethesda game is fitting.

For me it’s the text formatting.

Why can’t I express a pretty table unless pasting it from xls?

Why code blocks are useless and unreadable.

And how HOW do I exit a quoteblock if the quote reach the last line. ( I now always type a character on the last line before starting a block quote )

Call themselves are fine, not great, but damn. Writing text is reminding of text formatting in early version of ms-word.

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

#709

Earlier quoted context omitted.

You should try searching for a message in teams, and then finding the context (not just one message before/after) of the message. It just doesn't do that lol.

as opposed to zoom that doesn't even have a search?

I didn't realize this was a zero sum game where if Teams needs something Zoom needs to have it first too?

I don't use zoom, I use teams. Try again perhaps.

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

#710
I use Teams a lot with some Zoom. I've also used all the competing tools - Slack, whatever the current Google branding gives, among others. They all kinda suck. But hang on, am I asking too much? Is this suckiness because it's hard to do well? Oh, and add in that we all need to use it, all day, every day, so _any_ friction really annoys.

Distributed, connected collaboration in real-time, at (massive) scale - it's a big functional domain. Offering video, chat, document storage, sharing and collaboration, as well as project management and integration into a plethora of other apps and tools. This is surely a hard space.

Just look at apps that inhabit much, much simpler function spaces - say, Twitter, given the start point of the discussion. It doesn't get that glare of all day, everyday work use. It doesn't have the function and criticality to people's day. Twitter is down? It's just not a thing 99.9% of people will freak out over. Post-pandemic, Teams or Zoom is down means loss of a sales, key workshops stranding participants, distributed Teams losing comms during critical releases, and the list goes on.

Post reply on HN