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.
No post body was provided.
Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
81–90 of 1001 posts
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#82Surprised how sceptical all the comments here are. Dick or not the guy has a talent for building companies
All those hackers could better spend their time teaching children code or something if that not already the case...
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#83I'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.
[deleted]
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#84Earlier quoted context omitted.
They were asked to print their code and typically this is done as part of diligence _before_ closing. This is not sop. It’s Elon making a show of things.
Very rarely does due diligence involves actual critique of code on paper. Or code reviews at all, for that matter. Edited: technical review isn’t code review.
this is literally not true. nost diligence has a technical component, esp in M&A (vs. early-stage)
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#85> One former Tesla engineer, who spoke on the condition of anonymity to candidly describe the matter but was not involved, said Tesla engineers would have trouble capably assessing Twitter’s code. Distributed systems, the large-scale and spread-out network that Twitter is composed of, are not the automaker’s specialty, the person said. > The “idea of Elon being flanked by his Tesla engineers reviewing Twitter code is…
Isn’t twitter a pretty simple thing… db with writes and reads… it was maybe still is rails? I don’t know MySQL , Pgsql have come a long way and most of the hard parts would be scaling these services…. Keeping good caches in memory with redis or memcached… not really sure I see twitter being all that crazy other then it being so many people and so many years of edge case handling they would be hard for an outsider to…
"It's just a simple matter of programming"
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#86> One former Tesla engineer, who spoke on the condition of anonymity to candidly describe the matter but was not involved, said Tesla engineers would have trouble capably assessing Twitter’s code. Distributed systems, the large-scale and spread-out network that Twitter is composed of, are not the automaker’s specialty, the person said. > The “idea of Elon being flanked by his Tesla engineers reviewing Twitter code is…
Isn’t twitter a pretty simple thing… db with writes and reads… it was maybe still is rails? I don’t know MySQL , Pgsql have come a long way and most of the hard parts would be scaling these services…. Keeping good caches in memory with redis or memcached… not really sure I see twitter being all that crazy other then it being so many people and so many years of edge case handling they would be hard for an outsider to…
Hahaha. No.
They switched to the JVM eons ago. Also, you are severely underestimating how difficult it is to build and run something like twitter at scale.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#87Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#88Was the code printed on paper?
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#89For a variety of performance car nerd related reasons, I’ve not paid too much attention to Tesla. But iirc, there have been a couple threads here and elsewhere about Tesla making “expedient” choices in Eng, with a lot of horrible bodges around critical components. It definitely left me with an impression that Tesla was a place with low engineering quality — though again, I have no source at hand here, and don’t feel…
Tesla Model S owner here. The software on iOS and car is several years ahead of the competition. It embarrasses luxury German automakers. It’s made with the user in mind, it is elegant, and it is innovative in many surprising ways. For balance, there have been bugs - the linking of key fobs to driver profiles has always been glitchy, and Tesla’s decision to use an inadequate eMMC chip was shortsighted given the volum…
Not a Tesla owner. I sat in a demo Tesla. Infotainment UI looked clumsy. There was no Apple CarPlay. The most basic things didn't have knobs and required touch screen to use. Usability was years behind everyone else.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#90This is pretty standard procedure when a company gets bought. The new owners will conduct a review and decide who to keep and who to get rid of. They have probably been given a target of how many people they want to lay off and are evaluating who is worth keeping. It’s not worth staying at a company that gets acquired, you’ll either get laid off or be asked to do the same work with less people, and awful morale.
Respectfully, very little of this seems to be operating by standard procedure. Have you seen the incoming CEO ask people to bring printouts of their code, ever?
Musk is reportedly looking to cut deadweight before Nov 1st when equity vests -- with layoffs possibly happening over the weekend. He might already have a basic idea of key teams and for non-key teams he might be looking to cut very fast.
I absolutely have done things like this when acquiring companies - sat with people, asked them to basically interview for their own jobs while showing me the most important thing they wrote in the last quarter. I've done this at a much smaller scale, one on one at the employee's desk, because the companies I've done this with have been 1/10 or 1/100th the size of twitter.
I can see why it might make sense to just tell people to print stuff out to demonstrate competency, if you're otherwise planning to cut their entire department. Everyone gets a quick conversation with an engineer to talk about the code and gauge basic competency. If you don't suck, you stay. Seems not super crazy.
It especially makes sense if you've locked out everyone aside from previously identified key personnel to prevent sabotage.