Live data from Hacker News

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

washingtonpost.com

691–700 of 1001 posts

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

#691

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.

I wish Elon Musk all the best handling whatever this is with a skeleton crew of people who hate him on Tuesday: https://xeiaso.net/blog/openssl-3.x-secvuln-incoming.

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

#692

Earlier quoted context omitted.

You'd arguably have a case that Musk is not acting in the interest of Tesla and is using his Tesla position to enrich himself rather than the Tesla company. Exactly what the "CEO is supposed to serve shareholders" is all about.

There’s the presumption here that Tesla is footing the bill. For all you know Tesla hired out of these workers on contract and the Twitter is footing the bill.

Either Twitter footing the bill or maybe he pays Tesla for the project out of his own pockets.

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

#693

I don't at all object to code reviews/evaluation, but the thing I wonder about is this: I rarely open an empty file and write some big block of code. 98% of the time I'm fixing bugs in legacy code or shimming in some new feature. It would be trivial to produce the diffs I generated in the past 30 or 60 days, but the volume of code isn't really a great metric for my productivity. There may be some three line change th…

I once reviewed code for a company that got purchased. I took less than a few hours to reach conclusion. There were 7 developers and in 2 months only one was writing code. The entire team but that one developer was fired. Twitter has grown a reputation for being slow and a rest and vest haven. Won't be surprised if they are looking for people not writing code. On a different note, If you're in a large org and all you…

People leave jobs. If you're working at a company that's decades old, the people who did create the bug might have left the company 20 years ago.

I don't know for your job, but at mine code is supposed to stick to teams rather than people, so even if the people didn't leave the company, they probably changed teams and don't own the code anymore.

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

#694
what a waste of everyone's time. as a manager, I can tell you that even my smartest engineers go through highs and lows in their career and there are days when they push out code like there's no tomorrow and days when they don't push out anything because you know there's life outside of work that affects them (their dog passed away or their wife filed for divorce or their daughter is sick and was taken to ER etc). An arbitrary 60 days look back makes no sense.

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

#695
post #564

Earlier quoted context omitted.

>Musk has extraordinary capability of extracting every bit of potential a person can deliver. Either you work crazy at your 200% or you are worthless and the company is not for you. You are simply paraphrasing exploitation. >but if you see most of his businesses, his expertise is dealing with governments, contracts and policies makers Looks more like brute force and public shaming to me.

Anyone capable of doing software engineering for TSLA isn’t being exploited. They can take home an upper class income working for their choice of the cream of the crop of tech companies. It’s like an outside observer complaining that MIT exploits students because it’s expensive and the students have to do hard work. Well, of course. That’s what you agree to when you go there.

I doubt that both, Tesla engineers and MIT students, work crazy at 200%.

And it's a big difference between writing software for a car company and a social media service.

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

#696
post #57

Surprised how sceptical all the comments here are. Dick or not the guy has a talent for building companies

Can you elaborate on this argument? I don't really understand his companies as "well built" in any reasonable sense that I can identify. "His companies make him and many of his investors wealthy" sure, no disagreement from me. But "well built" is a different metric, and I think that's highly arguable.

Yes, his companies are completely sloppy and grossly incompetent. They only delivered 343,000 vehicles last quarter, which is way less than they should have, and the wait on a Model Y is close to a year, indicating extremely poor planning. Total joke of a company.

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

#697
post #440

Earlier quoted context omitted.

It would be reasonable for Twitter to pay Tesla for the audit work, because otherwise it would be a misuse of Tesla resources to only benefit the Tesla CEO.

Even if TWTR paid TSLA, this is still an obvious conflict of interest.

This is scraping the bottom of the barrel.

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

#698
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.

Would you also be outraged if those engineers were given an extra day off instead?

A day off improves an engineer's work-life balance in a small way. A day at a different company is different - it's a day that's neither productive to the original company nor restful to the engineer.

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

#699

The most bizarre aspect of this was when Twitter engineers were told to print out their code on paper. There is literally no good reason to do that. At best it is staggering incompetence. At worst it is an intentionally pointless and expensive exercise that serves purely as a loyalty test.

It's easier than giving source code access to all the outside staff that are coming in to actually read it. But it doesn't really sound like it's a meaningful review, since "last N days" of work isn't useful without context, and only people on the team can give them that.

It's truly bizarre.

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

#700
>Inside Twitter, in a highly unusual arrangement, engineers from Musk-led Tesla were examining the company’s code as the tech executive sought the input of his technical experts he trusted.

I would have expected they already did that prior to the acquisition.

It seems the acquisition was a blind buy.

Post reply on HN