Hacker News new | ask | show | jobs
by that_guy_iain 1303 days ago
> Why is it the employees fault for being disengaged but not Elon's for being an absolute clown and bullying/firing everyone via twitter that calls him on his bullshit. He's the one being toxic, but people responding negatively to toxicity are the "drain".

Who says it's their fault? If you fall out of love with your SO and want a divorce, is it their fault? No. But you still need to get a divorce.

It's a business. You shouldn't take anything personally. And employees were posting shit about Musk on Twitter before he even took over.

> If someone tells him 1200 server side service calls are making the app slow in one country and not another, he deserves to be clowned on. He's the one making the claim he's some sort of Tony Stark, so he can catch flak for being dumber than the average mid-level web developer.

On the same note, the Twitter tech team needs clowned on for telling him that. As well as, the fact they have a GraphQL making 1200 calls.

> Another corporate simp acting in bad faith. Nobody cares more about twitter devs making 300k not getting lunch more than Amazon abusing warehouse workers. Nobody has said that. Nobody has implied it. The same people who are decrying workplace toxicity in elon's takeover of twitter, ime, are in favor of Amazon Unions and better workplace practices.

The same people decrying Twitter and moving to Mastadon and other platforms are the same ones still buying from Amazon.

Amazon go union busting and people did nothing really. Musk fires people for publically disparaging the company and I hear about it non stop for days and days.

> If you give a shit about Amazon and it's mistreatment of employees I have literally no idea why you're doing so much work defending Musky boi.

There is a big difference between almost slave labour and firing people who make a lot of money.

The so-called defence of Musk here is merely pointing out the facts.

Facts:

* Making sweeping changes and have a month or so of chaos is better than months of chaos.

* Getting rid of disengaged employees is good HR.

* 1200 RPCs via GraphQL is still crap.

2 comments

you don't know employees were disengaged. You only know that they don't like elon musk. Twitter's culture was one of staunch criticism to make sure good products were being built in lieu of ego-driven development. This points to very ENGAGED employees.

Twitter runs impressively quick (or it used to at least) for what it does. Judging a system by something like "Woah 1200 calls, that's a big number" without contextualizing it just telegraphs your naivety.The "tech team" that told him that are literally the group of Tesla Engineers he brought in on week 1. So idk why the twitter team needs to be clowned on. He's been installing his own people the entire time.

Also, his sweeping changes are still causing chaos because they have a whole system in place now to re-hire people that were accidentally fired because Musk is firing people so much. It's been more than a month and people are still having to randomly fly to the office and do unscheduled group code reviews with like 4 hours of notice.

"People did nothing really" shows how disengaged you are from Amazon's criticism and the action people are taking against it. Christian Smalls is still out there working to Unionize Amazon, people are still supporting him and people like him. It's a long boring fight and just because it isn't flashy doesn't mean nothing is happening.

"People have a penchant for talking about recent news, I'm shocked"

They're not mutually exclusive topics. Billionaires exercising unilateral control over people's lives is generally a bad thing, whether that's musk or bezos.

1. 1000 RPCs is nothing surprising in any large solution. There are layers and layers of specialized services that are called parallelly and asynchronously. Can a "local" service handle everything by itself? Check internal datacenter letencies. Most of the calls are culled by caches anyway. Also those calls are made with Thrift/Protocol buffers/gRPC. Such design allows scaling, resiliency and prevents breaking other services by circuit breaking. I could go on and on.

2. How do you know that Twitter employees were disengaged?

> 2. How do you know that Twitter employees were disengaged?

Some are posting "kiss my ass Elon" on Twitter. Other's tweets mocking the code review and "hardcore" engineer stuff. I'm sure you're going to say "But that doesn't mean all of them" but Musk hasn't fired all of them.