Live data from Hacker News

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

washingtonpost.com

661–670 of 1001 posts

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

#661

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.

The new owner knows this, that the whole company is itching to self sabotage and crash twitter if they can..

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

#662
post #65

I'd be pissed off if I were a TSLA stock owner. Is Twitter paying Tesla to contract out these employees for their work? Otherwise, it's tons of thousands of dollars Tesla is pissing away on behalf of the CEO's side-hustle.

> Otherwise, it's tons of thousands of dollars Tesla is pissing away on behalf of the CEO's side-hustle.

Seems like a drop of water. For something to be legally relevant it has to be significant.

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

#663

Earlier quoted context omitted.

I'm not pissed and I am a stockholder. To me it makes a lot of sense. I doubt they are reviewing the entire code base. It seems like Elon is particularly interested in the automated systems that control content and detect bots. To that end, Tesla has a lot of expertise in AI systems.

The key is whether or not Twitter is compensating Tesla (and therefore its shareholders) at a fair market value for the time and resources used by Tesla employees for the benefit of Twitter (and therefore Musk as its owner). Not whether or not it makes sense to do so. If its a dumb idea on Twitter/Musk's part but Tesla is fully compensated for their engineers' time, all is OK. If its a great idea but Musk just assign…

There is no definition of "fully compensated"

Even if Twitter is paying much more than their salary costs, you still need to value the damage to the business by taking the crew away from the ship.

You can't just assume zero impact unless this was just a one-day workshop.

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

#664
post #497
post #492

Tesla software engineers still have not managed to get their FSD shit working, I don't see how this would help Tesla nor Twitter.

I think FSD is a couple magnitudes more complex than Twitter

That's exactly my point. Get your own shit working before wasting time on another company's shit.

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

#666

A great attempt to dodge vesting schedules and escape doling out severance. Even if they convince many engineers to quit willingly, one presumes that the next step is rounds of layoffs with cause . California is at-will, but notoriously anal regarding mass-layoffs. My serious question is, regardless of with or without cause, surely some employment attorneys are licking their lips at the stack of prospective cases the…

> If I was a Twitter engineer, I'd be trying to figure out how to maximize my severance package right about now. Absolutely. This is how I would spend every minute of my workdays until the eventual layoff. It’s a degrading experience for sure, but it could pay off big.

What are some strategies for this? I can't think of any and would have been a sitting duck.

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

#667

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…

I would say it's pretty "special" and well written code if outsiders can come in and quickly understand it. You should have commended them for their work.

I was coming here to say this. I have definitely found myself reading a codebase that is easy to read and easy to follow, and mistakenly concluding therefore that its developers were not solving complicated problems.

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

#668
Tesla has very mediocre computer vision AI. I am not an ML engineer, but how does that skill set translate to probably a series of ML programs optimized for very specific problems - for account take overs, for spam, for hate speech, for bots, for profanity, payment frauds, identity frauds. It’s not like computer vision suddenly makes you an expert on what features will maximize precision and recall for a spam detector

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

#669

A great attempt to dodge vesting schedules and escape doling out severance. Even if they convince many engineers to quit willingly, one presumes that the next step is rounds of layoffs with cause . California is at-will, but notoriously anal regarding mass-layoffs. My serious question is, regardless of with or without cause, surely some employment attorneys are licking their lips at the stack of prospective cases the…

> I'd be trying to figure out how to maximize my severance package...

How would one go about doing that? Is there a way to have influence on that?

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

#670

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.

Isn't Peter theil launching a competing product. Maybe he tricked musk into buying twitter so this happens
Post reply on HN