Did the Twitter engineers get any kind of retention deal? If I were there, it'd take a lot to convince me to stay with this kind of thing going on.
Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
461–470 of 1001 posts
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#462Earlier 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.
Plenty of companies with the same owner contract with one another. It's extremely common. When they're in the same industry, we call it 'vertical integration'
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#463This is a very stupid thing to do. First, code is not the issue. Code can be rewritten in not a lot of time, when you have clear what to write. Twitter is not something so complex, in principle, thus it shouldn't be that difficult (a team of 10 good programmers in a month can probably rewrite everything). The thing where is 99% of the complexity and you can't redesign in a month is the infrastructure, how data is sto…
Here’s just what Twitter has open-sourced: https://github.com/orgs/twitter/repositories
Laughable that you think 10 people can rewrite all of this in a month. It would take longer to scope out the design docs alone.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#464I think people are looking at this the wrong way. It's not so much about the code as it is about establishing an authority. Musk takeover is often regarded as banditry and I wouldn't be surprised if the employees didn't take him seriously in the beginning. This is his way of saying, "I don't trust you, I don't know what you have been up to but things are going to be different so better get used to it." Using Tesla en…
Every company I was with when it sold had lawyers come in and inform everyone that all processes are frozen, no equipment can move or be transferred while inventory is taken, everyone involved with computers surrender their passwords to their incoming engineers... etc, etc, etc. It is standard practice and there is nothing nefarious about it.
Tesla didn't buy Twitter, as far as we know though. Seems grossly inappropriate.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#465Earlier quoted context omitted.
You’d only be pissed off if you had a predisposition to dislike elon and then why would you be a TSLA shareholder? This is a tiny amount of money compared to the daily cost of running TSLA and would have zero actual impact to shareholder value. If it isn’t being accounted for correctly, there will be a tiny investor lawsuit and a tiny amount of money changing hands. This is latching on to just anything to complain ab…
So you have no problems with employees stealing the odd petty cash here or there for their side hustle, right?
As a shareholder? No. Tiny losses are not of concern to me. I am concerned with large scale long term outcomes not obsessing over not losing hundredths of a percent of revenue.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#466Earlier 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.
Sure but who is going to realistically enforce any kind of consequence?
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#467I 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…
Exactly, more code isn't better
Not only that, less code is better. The elegant and performant solution is the simple one, for example wireguard vs openvpn.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#468Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#469Earlier 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.
The counter argument is that Tesla has created more shareholder value over the past few years than any other single company, and in fact more than a ton of whole market segments. I mean, investors know he's sort of a loon, this is hardly the weirdest thing he done[1], and they're still on board. And FWIW: if you really want to structure this in a shareholder-friendly way, Twitter can just pay Tesla a consulting fee.…
that announcement most certainly did spook the market and news about the Twitter acquisition has been a drag on TSLA all year. You may have noticed the stock trading for slightly more than half of its peak value.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#470I think people are looking at this the wrong way. It's not so much about the code as it is about establishing an authority. Musk takeover is often regarded as banditry and I wouldn't be surprised if the employees didn't take him seriously in the beginning. This is his way of saying, "I don't trust you, I don't know what you have been up to but things are going to be different so better get used to it." Using Tesla en…
Why would anyone take him seriously when he is making a massive embarrassment of himself on his first day on the job (after doing the same for months leading up to the takeover?)
Musk didn't know the bio of the CEO of the company he was buying (who was also former CTO, engineer, Stanford PhD (thesis topic: making decisions under uncertainty), IPhO gold medalist, top tier Indian tech student) and called him a non-technical "manager type" and refused to ask him any technical questions.
I am also excited, because I think Twitter needs to end and Musk is the perfect person to destroy it.