Google over-hired talent to do ‘fake work’, claims Keith Rabois
finance.yahoo.com
finance.yahoo.com
Twitter's problem was cash flow and avoiding getting margin called amid falling ad revenue, high expenses and interest payment obligations, all related to Elon's buyout. They needed to stop the bleeding, and fast. Large tech corps are meanwhile sitting on hundreds of billions of dollars in their bank account and posting profits of tens of billions every quarter. It would be idiotic to further disrupt their operations for no reason.
Should Google do more rounds of layoffs, kill employee morale, increase overwork and burnout, shut innovative businesses, send talent to competition and significantly weaken the company's long-term prospects, all for a few hundred million in payroll savings that will go towards stock buybacks? The sad part is that the activist investor class will reply with a resounding – yes.
Not investing in a toxic and volatile shit show is a good investment strategy.
My father threw a lot of money into Tesla and is breaking even. His entire life is consumed with "oh shit what did Musk say now"
At that scale, there will always be inefficiencies and imperfections. I also don't think a big mass firing was a smart move long term, but it does make some investors happy for some reason, and gives a short term stock boost.
In a bull market, large companies don’t want the negative publicity that comes from layoffs. So instead of firing them, they get shifted into underperforming teams.
The axeman cometh with the bear market. That unwillingness to tell people you’re cutting costs suddenly becomes exactly what they want to hear, so you take the opportunity to get rid of all those underperforming teams.
It’s garbage collection at an organisation level. This is capitalism.
I work at Google. I've seen this one time. A manager didn't want to do the hard work of firing somebody on their team and then misrepresented their productivity to another manager when that person tried to switch teams. This manager received a bad performance review and left the company (I don't know if it was their choice).
It is easy to move teams within Google (or, it used to be at least). But it is very hard to move teams within Google if you have bad performance reviews. You can't really shift underperformers to underperforming teams at scale.
Tech has the worst P/E ratio, even big tech. It is fine if the value is inflated for disruption and future growth, else the valuation should be less than half of what it currently is if we say $1 of tech profit is equal to $1 of any other profit.
Google brings 1.30$ after tax for each 1$ invested into operations and it trades at 19.5 P/E. This is very conservative.
You think that guy builds anything with his hands?
He's even more removed from anything useful being done, he's not even the one doing stuff on a screen, he uses his screen to tell other people to do stuff on their screens.
Real rich having that complaint come from him of all people
synbio? green tech? crypto? adam neumann? you're gonna have to be more specific
1. Creating needless technical complexity.
2. Creating needless compatibility issues.
3. Distracting the focus.
So over-hiring isn't just a waste of money (which G has plenty of), it is also a waste of time (which G can't afford with competitors, like ChatGPT, breathing down it's neck).Hiring 2X more people is not going to result in 2X more value creation, but laying off half the staff is not going to 2X the productivity either.
"There's nothing for these people to do —it's all fake work. Now that's being exposed, what do these people actually do, they go to meetings."
I think I see the problem, workers are taking over tasks traditionally reserved for middle and upper management: entitlement, desk-sitting, inane meetings, LARPing as people who have real work to do.
The difference being that for people with actual talent, the state of affairs is intolerable. So you have to wonder what kind of efforts management were exerting to prevent these capable hands from being set to necessary work (of which there is plenty).
Then again, if you've ever worked in the tech industry, you needn't spend too long wondering since your own experiences will furnish you with more examples than you would want to enumerate, lol.
As a result, the people that work have to take on themselves an additional unpaid responsibility the actual restorative work or, at the very least, the emotional labour of pretending the mess being cleaned up wasn't made by someone, and just fell out of the sky.
This leads to a syndrome called "burnout" and "staff turnover" far more often than it leads to "open revolt". You can't have an open revolt of one (that's just called "a mad shouty fucker who can't hack it"). And you can't come together with others to revolt if you're unsure to what extent people have internalized the state of affairs as being their own fault, or at least, being something that is not okay to be discussed (either for fear of retaliation, or they've internalized the notion that it's an unsolvable personality conflict and the done thing is to be polite).
I know everyone is waiting for it to crash, and you may be right, but so far, stripping (hundreds of?) millions of cost out of the business seems to be have been a good strategy from a technical perspective at least.
The other 80% are focused on new product features, growing revenue, growing engagement, growing new user signups, l blocking bad actors and legal compliance.
Axing all of those roles could make it easier to ship valuable user-visible features, since the remaining engineers wouldn't have to work around feature flags for fifty ongoing experiments.
They launched Twitter Blue which was a disaster, then redid the timeline, which at best is a mild improvement, and they rushed out things that were already in development.
I'm not in the Twitter Death Cult camp, but I don't think we can judge new development based on the last four months.
Core services for Twitter have been throwing 500s a dozen times every few hours. [2]
Twitter performance for users in Australia has fallen apart twice due to what was found out to be someone losing access to a root certificate and mitigation delayed because the team that could fix it is no longer employed. [3]
This is far more than a few stability glitches.
[1] https://deadbird.singlepane.io/d/hI9vrUO4k/home?orgId=4&refr...
[2] https://deadbird.singlepane.io/d/hI9vrUO4k/home?orgId=4&refr...
[3] https://deadbird.singlepane.io/d/hI9vrUO4k/home?orgId=4&refr...
Musk’s handling of Twitter has also been pretty poor by all means.
People have been treating this like some political issue with sharp partisan divide. Which I don’t get at all - it’s a badly run business taken over by a new boss who is out of his depth. Nothing more, nothing less.
That said, for the casual user, Twitter works pretty much the same as it did before he took over. It hasn't crashed durably. Makes one wonder what all those people were doing.
Twitter has some insane infrastructure, which was way ahead of it's time, and which is arguably why the company is still doing fine.
A "good" social media giant needs huge headcounts in departments like Troll Control. Last I heard, the EU was threatening to sanction or ban Twitter - because the gutted Twitter staff wasn't keeping up with such things.
I think it's possible trolls, spam and "bots" exist in a kind of invisible state: they can be found if one looks for them (what regulators are probably doing) but they never appear on most users' timelines.
Sexual harasser Keith Rabois? http://www.huffingtonpost.com/2013/01/26/keith-rabois-square...
Founder of effectively bankrupt OpenDoor Keith Rabois? https://www.nasdaq.com/market-activity/stocks/open/advanced-...
Anything that isn't immediately profitable is fake work, anything that fails to work out means that it was also fake work.
Instead, we're lamenting that a company should "at least be trying" to pump more sewage into the river we all drink from.
What a sad state of affairs :)
The more robust security basis for the platform is a much stronger claim, and remains true as hardware and software change around it. E.g. we can improve the security of a platform by adding CHERI say, and that improves the security of a linux+android based system, but fuchsia would also get those wins on top of the existing more secure basis - the gap may be reduced but fuchsia stays ahead.
So the goal is to create a platform that is more profitable in the long term, so not "fake work".
It would appear that Google decided that there has not been sufficient evidence of success to warrant any further investment, but that does not mean it is "fake work".
Such a definition of "fake work" would mean that any project that you should never do or attempt anything if you do not have guaranteed success.
Note: Google's business model is ads. Android exists for the purpose of selling ads. The long term goal of fuchsia under this model would be a cost reduction in the maintenance of some android style product (whether it would still be branded android shrug). That's the business argument for fuchsia, and it would appear that google has decided that it doesn't think the end result is likely to warrant the cost of getting there. I think that's a shame, and I feel bad for my former coworkers, but I can't say "companies should be required to continue developing projects forever, even if it appears they won't succeed in their goals" because that would also be dumb :-/
In general, OS release 1.0 takes about 4 years. That's feature complete and ready for users, not necessarily production ready and stable.
And it runs on a kernel that started development on 1991. Also, Fuchsia is already running in some devices, - https://arstechnica.com/gadgets/2021/05/google-launches-its-...
Like we have a bunch of those under each tree in a park...
Instead they had 400(!) full time staff pulling in $300k+ developing something which nobody wanted and has not had any meaningful impact.
Maybe in 10 more years they will manage to replace Android…
Yea we slack off but nothing like this.
So happy seeing this lmaao