Earlier quoted context omitted.
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.
Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
761–770 of 1001 posts
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#762Earlier 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.
If Twitter is paying above fair market rate, that's collusion to benefit Tesla at the expense of Twitter.
If Twitter is paying exactly fair market rate, why does it need to be Tesla employees? That starts to look like self-dealing to make Musk's live easier.
You can't really win in this situation, which is why any sane executive avoids such a conflict of interest in the first place.
(I'm not claiming there will be any repercussions mind you - if Musk got away with SolarCity he'll surely get away with this.)
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#763I 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…
Larry Ellison famously once said "if you aren't a developer, and you aren't a salesman, then tell me real slow just what it is you do".
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#764I 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
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#765Earlier quoted context omitted.
If these numbers are right and they're laying off 50% the workforce, half of me wonders how much Parag could raise to build a new Twitter from scratch and just hire 500 - 1000 talented folks off the street for the venture, I mean if Travis K could raise almost a billion for his shitty ghost kitchen venture I'd have to think they could get enough runway to get something launched pretty quickly. There's so many "What w…
>half of me wonders how much Parag could raise to build a new Twitter from scratch That would probably amount in $0. Twitter wasn't profitable and part of it was its CEO. Why would investors be willing to lose money, especially in the current economic situation? I would rather wait for Elon to stabilize Twitter and go public again.
A whole bunch of genius investors just bought a company worth $11 billion for $44 billion...
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#766The point to accept here is:
He is outstanding in what he's doing. In everything. He is a business man and doing everything for getting the most out of that.
No matter if it's his "who pay for Ukraine/Starlink" -> he didn't get the 20th of millions from the government, but he tried it and in the end getting more funds from others.
Or his "lay of 75 percent" - he try to save some money which Twitter is burning ever since. He tries, with the help of his engineers, to find out whether it's possible to lay of so much and still having the company running..
So, the best would be here to ask why this way and not another? All the guys and gals are knowing what's happening. They are the best what could happen to Musk. So, this will be profitable in 6 weeks.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#767I 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.
A code review? TL;DR; LGTM, straight to prod!
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#768I'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.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#769The 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.
Or simply Elon is more unstable than Dogecoin and wanted to show new employees who is the boss, it was a really pathetic power move.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#770I can only imagine how bad this is for morale. Out of the blue code review conducted by an external company means total lack of trust.