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.
Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
281–290 of 1001 posts
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#282I 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.
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
#283Earlier 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.
Tesla is not his personal fiefdom. Stop.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#284Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#285Earlier 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…
oh that's based on my observation of comments whenever he comes up, like this one here right on this thread
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#286I’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.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#287If 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…
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
#288Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#289I’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.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#290Earlier 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..