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.
Nah paper is still more efficient than computers in quick meetings. You can imagine many seconds being wasted if they were on a laptop and the engineer needs to find his files. Paper the UX is perfect and instant.
Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
721–730 of 1001 posts
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#722Earlier quoted context omitted.
Love him or hate him, without Musk Tesla would have been dead in the water as a company and its shares would have been worthless by now. Those stock owners knew what they did when they got into TSLA.
> without Musk Tesla would have been dead in the water as a company and its shares would have been worthless by now I don't know how you could possibly know that, that's an unfalsifiable claim. I could make the opposite claim (that with a different CEO, Tesla would be worth ten times as much as it is now) and you couldn't disprove it.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#723I 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 100% object to code reviews in this way. If you have dignity as a developer you’d quit swiftly.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#724I 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 love being able to fix a bug with a one line change.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#725I 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 don't think the code review involves counting the lines. A reviewer can distinguish hundreds of lines of boilerplate from a non-trivial few lines change.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#726I 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.
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…
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.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#727I'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.
> Otherwise, it's tons of thousands of dollars Tesla is pissing away on behalf of the CEO's side-hustle. Seems like a drop of water. For something to be legally relevant it has to be significant.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#728Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#729I 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.
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…
Is Parag a startup entrepreneur, or more of a going-concern executive? Startup seems more Dorsey’s thing—who made more money on the deal and took his new social media effort out of stealth as soon as the Twitter sale was finalized.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#730I'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.