Live data from Hacker News

Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

washingtonpost.com

901–910 of 1001 posts

Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

#901
post #853

I worked at Facebook and remember what it was like to first face the total complexity of the system. It’s really hard for me to imagine myself working at a company that deals almost exclusively with machine-generated data (as Tesla does) and being assigned to judge a social platform’s engineering qualify in one day . Cars and spaceships on a closed network are fundamentally “clean” compared to having hundreds of mill…

[deleted]

Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

#902
Does Twitter have a large, observable quality problem. If there is one, I never noticed it myself but I’m not a particularly active user.

I think their main problem is they thought their role was thought shaping via sneaky algorithms. I think the main thing Elon should be looking to remove is those that fundamentally do not believe in free speech, since the culture of the company has changed so materially.

Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

#903
post #291

Earlier quoted context omitted.

What’s more funny is how people commonly believe like this their code is so special or different than everyone else’s. Reverse engineering a large code base is not anywhere as hard as most software engineers somehow believe. I was tasked with analyzing a large code base from a company that my employer had been an investor in and as part of their investment had been given IP rights, the company employees were floored…

The code is almost never special, the business processes are. Everything seems so incredibly trivial until you reach something that isn't.

At my last employer before retiring (not tech but used a lot) has a very unique (and way larger than Twitter) complex set of businesses. They change at an insane pace and often involve things that in the end don't ship, resulting in crazy complex code base networks. We also had 100's of teams building every kind of software imaginable (server api's, web apps, mobile apps, internal apps, hardware with embedded code, etc). Anyone from the outside coming in cold to examine the code would have no idea where to even start, much less be able to evaluate anything. It's not that any individual thing was necessarily complex, but there were so many interconnected business practices and related businesses that understanding how they relate is very hard for anyone who has been there for years much less someone from an unrelated industry.

For example you could look at my team's mobile codebases and probably figure out what was going on, but understanding all the services we consumed, and what they consumed, etc. (given the deep mix of micro services and macroservices) would make understanding the why of the entire system impossible.

Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

#905

I dunno why any Twitter engineers would be really trying that hard right now. Passively destroying Twitter from within by not trying, and trying to make a billionare lose 44 billion dollars is a significantly more fun and interesting challenge than making Twitter a better product.

Comments like this makes me lose faith i humanity. If I were a engineer at Twitter, I'd do my absolute best up to the minute I have to leave the premises. Because I would care about the company, my colleagues and most importantly for the >200m people who use Twitter for fun, educational, business and those who depend on it. But it's probably because I'm an old beard, who value being honest and ethical, to be the bett…

This is a laudable position. But consider that, depending on your level and immediate boss, you might not be in a position to survive the layoffs no matter how personally productive and impactful you are.

There will be a lot of snap judgements made by Musks engineers on who is to be spared and there are two major terms. One is how engaged and interested your current boss is at staying, and the other is what Musk’s technical staff think. Their judgements will be quick and driven by outcomes like broad attrition targets and what is absolutely necessary.

If your on an unnecessary team, but are a rockstar, you might not survive if nobody communicates your value. And it is very likely that entire divisions are on the chopping block. Without an ally on a surviving division that says “I need this guy moved to my team yesterday” it’s unlikely to happen.

Not saying you shouldn’t do the right thing, but try to understand the interests of and see what makes sense for you.

Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

#906

I dunno why any Twitter engineers would be really trying that hard right now. Passively destroying Twitter from within by not trying, and trying to make a billionare lose 44 billion dollars is a significantly more fun and interesting challenge than making Twitter a better product.

`git blame`

Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

#907

Musk sounds like a nightmare to work for. Why would any self-respecting developer stick around under these conditions? I expect an exodus of talent from Twitter in short order.

For there to be an exodus of talent there must be first be talent. From what I can make out Twitter's workforce are predominantly average at best and I suspect we'll see at least 2,000 or so people cut in the next 6 months.

Large group tends toward the mean, news at 11. Average engineers keep the world running. Most code that needs to be written does not meaningfully benefit from talent.

Losing all your tribal knowledge in any business unit is a mess. That’s the prediction. The talent at Twitter is likely already gone to another company for a raise. I’ve never seen the best engineers stick around after any acquisition.

Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

#908

Earlier quoted context omitted.

Cult of personality. Steve Jobs, Larry Ellison, Bill Gates etc. were all a nightmare to work when they were younger.

Well-behaved men rarely make history.

Yeah you can’t really turn this quote around like that because it drastically changes the meaning. Well-behaved means with respect to an establishment and not accepting one’s place as imposed by it. Being a dick makes you not well-behaved in the way you would describe a toddler.

Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

#909

Does Twitter have a large, observable quality problem. If there is one, I never noticed it myself but I’m not a particularly active user. I think their main problem is they thought their role was thought shaping via sneaky algorithms. I think the main thing Elon should be looking to remove is those that fundamentally do not believe in free speech, since the culture of the company has changed so materially.

Ex: With all the Kanye meltdown stuff going on, which is "general interest", Twitter has been amplifying the tiny % of antisemitic voices in the black community and mixing them into my feed. That is quite distracting for a site I use for various tech industries' news during breaks. (Common use case of Twitter, and big $ for them.) In contrast, a site like LI will only rarely allow, and more importantly, freely & widely amplify that sort of garbage - I can list the exceptions I've seen.

Jack Dorsey believes in injecting both sides to a conv even when one is fringe intolerant nonsense on something far from the topics a user primarily cares about. See his NPR interview on boosting both sides over in-network moderation in these cases.. which some not so mysterious reason correlates with engagement-boosting algorithms. (Double speak for: trolls drive clicks.) Listening to racist diatribes and being algorithmically nudged to 'engage' with it is ridiculous

Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

#910
post #900
post #863

Earlier quoted context omitted.

Yes, software is typically more complex than a laymen would expect once all of the edge cases and layers of legacy code or “guano” are implemented. However, I doubt that these outside developers are expected to understand everything in a single day. There are legitimate questions regarding how certain sections of the Twitter code operate as it relates to censorship, which is a primary reason Elon purchased Twitter. G…

In a typical acquisition this would have taken place under NDA during due diligence, before closing the deal. But Elon waived it. Now he’s apparently trying to find this shadowy “fifth column” of engineering over the weekend so they could be fired before RSUs vest on Tuesday. It sounds completely ridiculous but isn’t entirely implausible since, after all, we’re talking about the same person who committed $44 billion…

Elon has only been there for 24 hours.

It sounds like your not a fan of Elon and nothing he’ll do can change your opinion. Why not hold back the strong judgements and conclusions for at least a few months? Maybe he will surprise you?

Post reply on HN