Live data from Hacker News

Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

washingtonpost.com

281–290 of 1001 posts

Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

#281
post #154

If someone completely new to my codebase came along and tried to evaluate my code I'd laugh. You can't jump in and "evaluate" without knowing context and being familiar with the features.

I don't think Elon is trying to evaluate the code. It seems to me he is trying to evaluate people.

Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

#282

I 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 we should do" moments that are too expensive or deviate too far from the core business that don't get developed in most enterprises that could be pursued when starting from a blank slate.

Anyway, just a thought experiment.

Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

#283

Earlier quoted context omitted.

I’m a TSLA holder and I don’t mind at all. The everyday minutiae don’t concern me as long as the big picture for Tesla is in focus and with in reach

Quoted post unavailable.

No. It’s not. Musk bought Twitter and took it private. Tesla is still a publicly traded company that Musk (as I understand it) actually had to sell a non-trivially portion of his stock in in order to finance part of the deal.

Tesla is not his personal fiefdom. Stop.

Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

#284
tech stacks, especially of this magnitude run on processes, some machine some human some rube goldberg taped together combination of the two. Code is simply an artifact. 'Evaluating the code', sounds like a rather strange way to appraise the state of twitter's tech.

Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

#285
post #195

Earlier quoted context omitted.

> It's pretty clear to me that there are elements of the elite media-political complex that are terrified of Elon purchasing Twitter because he's not part of their crowd and they won't be able to control him and through him what is and isn't allowed on Twitter. IMO all articles about this should be read with that in mind. It's pretty clear there are elements of the Hacker News community who are obsessed with "cancel…

your strawman is that having a generally pro-elon disposition = thinking elon is some kind of infallible savior The reality is that the current moderation of major forums like Twitter, HN, etc is so one-sided that it produces whatever passive-aggressive posturing that we are engaged in with this very conversation. I am not going to make a defense of elon or his actions, but I will say that I believe there are two goo…

> thinking elon is some kind of infallible savior

oh that's based on my observation of comments whenever he comes up, like this one here right on this thread

https://news.ycombinator.com/item?id=33389206

Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

#286

I’m still looking for a concise term for “someone who claims to be an expert but immediately reveals beyond any doubt that they have no clue what they’re saying, simply by opening their mouth on the subject.” Having Tesla engineers over to review Twitter code is definitely that. It’s ridiculous.

Nassim Nicholas Taleb has referred to this concept as "epistemic arrogance". In "The Black Swan", Taleb defines it the following way: > Epistemic arrogance: Measure the difference between what someone actually knows and how much he thinks he knows. An excess will imply arrogance, a deficit humility. An epistemocrat is someone of epistemic humility, who holds his own knowledge in greatest suspicion.

Even better coming from Taleb (love him to bits but he's describing himself sometimes)

Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

#287
post #154

If someone completely new to my codebase came along and tried to evaluate my code I'd laugh. You can't jump in and "evaluate" without knowing context and being familiar with the features.

What’s more funny is how people commonly believe like this their code is so special or different than everyone else’s. Reverse engineering a large code base is not anywhere as hard as most software engineers somehow believe. I was tasked with analyzing a large code base from a company that my employer had been an investor in and as part of their investment had been given IP rights, the company employees were floored…

Really interesting story, approximately how many lines of code were in that codebase?

It's hard for me to imagine someone grokking a 10M+ line codebase without external help, but I've never tried it. I do agree with the assertion that most codebases are not as _special_ as they like to think.

Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

#289

I’m still looking for a concise term for “someone who claims to be an expert but immediately reveals beyond any doubt that they have no clue what they’re saying, simply by opening their mouth on the subject.” Having Tesla engineers over to review Twitter code is definitely that. It’s ridiculous.

Recall that Elon alienated Peter Thiel by insisting on Windows over Unix at PayPal. Thiel resigned.

Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said

#290
post #95

Earlier quoted context omitted.

Are we back to measuring performance in klocs? I can get you a bunch of incompetent devs that change hundreds ofines of code a day. All you need to do is change indentation and eols or just rewrite basic stuff too lazy to understand.

According to the engineers in the undercover interviews, a large part of the staff only work "when they feel like it", which would result in some taking months of paid time off or just hanging out in the office all day. kloc is not great as a general metric, but in this case it might make it obvious where you can trim a lot of fat..

I see and the issue lies with the engineers? If thats the company’s policy the whats the problem? He should change the policy and only then review performance in that context.
Post reply on HN