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

231–240 of 907 posts

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

#231

Post by Raed667 »

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.

Officies, especially the great ones (as in also very expensive) create an irrational emotional attachment and are very hard to downsize on them without impacting morale.

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

#232

Post by flappyeagle »

m348e912 wrote: post #86
flappyeagle wrote: post #52

Earlier quoted context omitted.

If I were forced to use teams I would quit. At least if you're laid off you get serverance

>>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'm on an M1 macbook. Teams is extremely bad. I don't know how to describe it tersely other than everything kinda sucks. I work remotely and take a lot of meeting, so it's like my office in a way... an office that's cramped, leaky, ugly, uncomfortable, and cold.

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

#234

Post by willcipriano »

it_citizen wrote: post #209
Bilal_io wrote: post #175

Earlier quoted context omitted.

Hence the need for an investigation. I don't think there is collusion, but I wouldn't be surprised. My conspiracy (let me put the tinfoil hat on) is that corporates and mega rich people wanted the recession badly because they can benefit from it. But it didn't happen so they're doing the layoffs and increasing prices to manufacture the recession despite their all-time high profits.

Genuine question. How would the mega rich benefit more from the recession than from a stable or high growth environment? Seems easier to capture a bigger piece of the pie when the pie is growing for everybody no and nobody complains? Not to mention the social and political unrest which might be triggered by a recession. Recent and old history has shown times and times again that it is when people go hungry or despera…

Wages lag growth, have a high growth environment for a few years and then cut off the faucet once people start demanding higher wages.

It may not be a conspiracy but that is what's happening.

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

#235

Post by nickpeterson »

adverbly wrote: post #184
nickpeterson wrote: post #51

Just wait till Microsoft starts charging a license for vs code and developers heads implode.

Hold on that could actually happen? It's not officially open source or anything?

Pretty easy, just release new features as paid plugins that need subscriptions and make minimal updates to the core program.

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

#236

Post by ilyt »

brookst wrote: post #198
savanaly wrote: post #166

Earlier quoted context omitted.

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?

I'm also confused because almost all of my company's Teams usage happens in unthreaded chats.

We don't use teams feature almost at all because it forces threading. Before wer used mattermost but teams is 100% worse but with video chat...

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

#237

Post by seti0Cha »

adverbly wrote: post #184
nickpeterson wrote: post #51

Just wait till Microsoft starts charging a license for vs code and developers heads implode.

Hold on that could actually happen? It's not officially open source or anything?

The code is opensource, but not the ecosystem. Microsoft is maneuvering towards the same position as Android with respect to Google Play. Not technically mandatory, but so many conveniences are built on it that it may as well be for anyone not interested in investing a lot of time finding workarounds.

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

#238

Post by ApolloFortyNine »

romellem wrote: post #101
mardifoufs wrote: post #25

Earlier quoted context omitted.

>i) Effective immediately, we will be moving laptop refreshes from three years to four years. ii) We will be moving to Microsoft Teams for the sole purpose of video conferencing, saving significant cost and simplifying cross-company and customer conversations Layoffs and having to use teams? Talk about a morale hit

I'm not kidding, one of the reasons I left my last job was when our parent company forced Outlook, Sharepoint, and Teams on us (vs. Google mail, Google Drive, and Slack). That change on its own isn't the worst thing of course, there were other reasons why I was considering leaving, but it was definitely one of the last straws. Those MS solutions are just worse than the competition, and getting frustrated at your bugg…

Gmail is so much better than outlook it's honestly insane. The way it handles email chains is infinitely better than outlooks, which often leads to responses just getting lost when someone replies all to a message that wasn't the most recent.

Honestly I wouldn't be surprised if this is 'our' fault, as I'm sure someone will point out. But in the years of using Gmail at my last employer, it just worked.

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

#240

Post by brazzledazzle »

c54 wrote: post #183
savanaly wrote: post #166

Earlier quoted context omitted.

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?

I think they’re just saying that teams forces you into using a thread, and make a choice to create a new one if that’s what you want. In slack by default you’re writing a top level message (ie creating a new thread)

Pedantic perhaps but maybe it's worth pointing out that Teams doesn't force you to use a thread. It just makes it the obvious choice since each top level message has a reply button directly on it so it's a single step process. Also when we're talking about Teams there's a big distinction between a Teams/Teams/Channel vs a Teams/Chat which is its own annoyance. They don't even support the same formatting capabilities (e.g. markdown) which is weird.
Post reply on HN