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

GitHub to lay off 10% and close all offices

twitter.com

Post reply on HN
Print view View original

361–370 of 907 posts

Re: GitHub to lay off 10% and close all offices

#361

Post by matwood »

brazzledazzle wrote: post #259
goalieca wrote: post #146

Earlier quoted context omitted.

Gsuite has the best collaborative editing.

What you don't like collaborating in the excel web app and wiping your coworker's active cell edit from existence by inserting a row somewhere above it? Next you're going to tell me you don't enjoy powerpoint web app randomly changing formatting in bulleted lists when you do something as complex as hitting enter to add a new line. You can tell where Microsoft spent their energies (outlook, teams, maybe onenote?) and…

> were sharepoint web apps

ARE still sharepoint apps. At least that's how they feel.

Re: GitHub to lay off 10% and close all offices

#362

Post by ghshephard »

agilob wrote: post #148
roboben wrote: post #27

The worst part of this is that everyone at GitHub is now forced to use Microsoft Teams.

I know I'm in the minority here, but I choose Teams over Slack any day. I much prefer thread-based chat than message based chat. Teams forces people to use top message as a topic, then respond to messages under that topic. Slack message is just a message. You want to search something on Teams, you get full threads, chat is part of documentation. You want to find something on Slack, you need to click on date of the re…

I'm guessing you have a different experience with slack than I have - because important channels are frequently set to "Alert" - it's extraordinarily bad behavior (to the point at which you are chastised and coached by your manager) - to ever respond to a message in a channel without threading. We have a broad array of "THREAD-PLEASE" Emoji's that you get hit with in the first week or two when you onboard if you do that.

We've taken it next level here - whenever there is an incident - not only don't you respond as a message in the channel, you get a new channel (created by a Bot when IMOC declares an incident) per incident, so all of the activity for that incident is self-contained (can be many, many thousands of messages) - and, of course, even in that split out channel (which is only talking about a single incident) - even there you need to respond on threads, never as a new message.

Re: GitHub to lay off 10% and close all offices

#363

Post by mshake2 »

JoshCole wrote: post #332
1-more wrote: post #269

Earlier quoted context omitted.

then nothing can ever be malice. This razor sucks.

It can, you just need to point out in what ways a thing is not adequately explained by stupidity.

Tell me the difference between stupid and illegal and I'll have my wife's brother arrested.

-Jared Vennett, The Big Short

Re: GitHub to lay off 10% and close all offices

#365

Post by jstummbillig »

softwaredoug wrote: post #201

I really liked Shopify's remote model of not closing offices, but turning them into "ports" for teams in major cities to get together throughout the year for planning, team building, and retreats. You had an official place to get together, enjoy the perks of tech company offices, but with the intention of deep short bursts of interaction rather than focused work.

That seems alluring. I wonder how large of a percentage of employees would, if prompted directly, opt to have company funds directed to have "ports" in major cities, if it was entangled with their salary.

Would you choose an additional 600$ a month and remote only, or would you vote for permanent variable spaces in major cities for events and team building?

Re: GitHub to lay off 10% and close all offices

#366

Post by [deleted] »

mrtranscendence wrote: post #353
m348e912 wrote: post #86

Earlier quoted context omitted.

>>If I were forced to use teams I would quit. It's funny to hear this because if I were looking for a job one of the selling points for me would be if they used teams. I'm on it all day, I present and run video meetings on it. I use it on different devices. It's not perfect by any means, but I'm confident that it will do what I need it to do. My only guess is you're on a linux desktop and you don't use an enterprise…

I use Teams on a relatively modern Intel MacBook Pro. My chief complaint is that it murders my battery -- I barely get two hours when I'm on Teams video calls. But there are other issues. For example, sometimes the window just disappears when it's in the background. When that happens I don't get any notifications, so unless I notice that Teams has bugged out I'll miss when someone tries to contact me. And recently, v…

[deleted]

Re: GitHub to lay off 10% and close all offices

#367

Post by krzyk »

savanaly wrote: post #166
agilob wrote: post #148

Earlier quoted context omitted.

I know I'm in the minority here, but I choose Teams over Slack any day. I much prefer thread-based chat than message based chat. Teams forces people to use top message as a topic, then respond to messages under that topic. Slack message is just a message. You want to search something on Teams, you get full threads, chat is part of documentation. You want to find something on Slack, you need to click on date of the re…

I'm quite confused because almost all conversation in my company's slack happens in threads. Maybe your impression of Slack was formed in a time when they didn't have threads?

Slack threads are hidden, it is clearly visible that they were added later.

I prefer how they are handled in zulip.

Re: GitHub to lay off 10% and close all offices

#368

Post by mrtranscendence »

mrtranscendence wrote: post #353
m348e912 wrote: post #86

Earlier quoted context omitted.

>>If I were forced to use teams I would quit. It's funny to hear this because if I were looking for a job one of the selling points for me would be if they used teams. I'm on it all day, I present and run video meetings on it. I use it on different devices. It's not perfect by any means, but I'm confident that it will do what I need it to do. My only guess is you're on a linux desktop and you don't use an enterprise…

I use Teams on a relatively modern Intel MacBook Pro. My chief complaint is that it murders my battery -- I barely get two hours when I'm on Teams video calls. But there are other issues. For example, sometimes the window just disappears when it's in the background. When that happens I don't get any notifications, so unless I notice that Teams has bugged out I'll miss when someone tries to contact me. And recently, v…

Oh, it also plays poorly with virtual desktops (or whatever the feature is called on MacOS). If I switch from the desktop with the Teams window to another desktop, then cmd-tab back to Teams, it will switch the active application to Teams but won't switch back to the desktop with the actual Teams window. This is infuriating.

It seems to have something to do with the fact that, when on a call, Teams is active in every desktop (with a stupid little video window). But it persists even when you're not on a call.

Re: GitHub to lay off 10% and close all offices

#369

Post by krzyk »

Smaug123 wrote: post #356
tomtheelder wrote: post #348

Earlier quoted context omitted.

Slacks threading model is super weak compared to other options. I haven’t used teams, but I went from Zulip to Slack a little while ago and it felt like a huge step backwards.

Zulip is in a league of its own, though - I'd say Slack is pretty similar to other non-Zulip options.

Regarding threads I've seen two options (besides zulip state of the art handling of that). Either hide the threads like slack or throw them in your face like Cisco webex teams.
Post reply on HN