Based on a few articles I've read, it appears he may be bringing developers from Tesla into Twitter but I have not seen anything from him directly stating that. I doubt they will hit the ground running but with time can probably dig into the code and processes.
Sadly I've been in an industry that was focused on taking over after entire IT/engineering/development teams were let go. As rough as it is for the people let go, it is equally demoralizing to pick up the pieces from people either being let go or that were let go. It can be done accepting it will be rough around the edges at first. During the dot-com bust I was one of the people that had to sit with the soon to be let go team members and document their job and automate as much of it as I could. That's all I did for a couple of years.
If Musk is actually using Tesla devs at Twitter he better have a rock solid contract for service between the two companies. Otherwise he opens himself up to a shareholder lawsuit for misuse of Tesla corporate resources.
U wot. If Tesla engineers do work for free for a company owned by one of the shareholders, there's clear damage there in the form of misallocation of resources.
Uh huh. Let’s say Musk writes himself a check from Tesla for an extra $100,000. He cashes it, but the next day TSLA is up. No problems there? No legal risk?
Now let’s say that instead of a check, he gifts himself $100,000 of Tesla engineering time.
I've done that too, it really sucks. My boss wasn't thrilled about it either but it was a directive from a lot higher up than she was. I took that as cue to look for a new job myself, as did others. Not everyone left but enough such that between the layoffs and the devs/BAs that quit caused a project to slip such that they had to pay "fines" as designated in the contract and a couple senior leaders were let go.
In UI, there's a lot of overlap. A lot of Apple people went to Tesla to build their touchscreen. Those people are qualified to work on the Twitter app itself.
Taking your comment in good faith: A lot more engineering goes into "make people click on ads" than you seem to be realizing. And like or not but monetization is at the core of Twitter's business.
If you meant my comment, I have nothing but respect for all engineers and developers. What I meant by not hitting the ground running is that Tesla engineers and developers would not have any of the tribal knowledge from within Twitter and if they were already let go it may be incredibly difficult for any person to reverse engineer things.
I'm talking in aggregates, of course I don't assume that because it would be totally illogical.
I'll be explicit in my assumption. If it were actually possible to rank engineers in some measure of productivity/effectiveness, the median at Twitter would be more product/effective than the median at Tesla. This gap would widen if we are talking about productivity/effectiveness at tasks necessary for Twitter's business.
I've met lots of MIT and Stanford students (can't say the same for Miami).
I've also met lots of Big Ten students, and UT Austin / Duke / Utah / U. Washington /SUNY students. We can compare one to the other in terms of analyzing & fixing software and I'll take that bet anytime.
Based on a few articles I've read, it appears he may be bringing developers from Tesla into Twitter but I have not seen anything from him directly stating that. I doubt they will hit the ground running but with time can probably dig into the code and processes.
Sadly I've been in an industry that was focused on taking over after entire IT/engineering/development teams were let go. As rough as it is for the people let go, it is equally demoralizing to pick up the pieces from people either being let go or that were let go. It can be done accepting it will be rough around the edges at first. During the dot-com bust I was one of the people that had to sit with the soon to be let go team members and document their job and automate as much of it as I could. That's all I did for a couple of years.