Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

washingtonpost.com

Post reply on HN
Print view View original

51–60 of 1001 posts

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

#51

Post by smt88 »

marstall wrote: post #26

I was thinking the "30-60" day time window may be a somewhat subtle way of catching out engineers who haven't written a thing in that amount of time. that would be one way to identify low-performers. not unproblematic by a long shot, but quick, and probably somewhat effective. and it wouldn't require any deep knowledge of twitter's codebase on the part of the reviewers.

Any slightly competent software leader would know that you can track every character of code written by any dev using version control.

Printing it out as a mark of honor/shame is something a petty, arrogant tyrant would do. Musk has been around people who are afraid to say no to him for too long.

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

#52

Post by uni_rule »

_vertigo wrote: post #6
jstx1 wrote: post #3

> One former Tesla engineer, who spoke on the condition of anonymity to candidly describe the matter but was not involved, said Tesla engineers would have trouble capably assessing Twitter’s code. Distributed systems, the large-scale and spread-out network that Twitter is composed of, are not the automaker’s specialty, the person said. > The “idea of Elon being flanked by his Tesla engineers reviewing Twitter code is…

From Musk’s POV, a bunch of solid, well-rounded, and experienced engineers you trust might be enough to tell you “this guy is full of shit” when talking to new people. Maybe it’s less about code quality and more about eng quality.

No post body was provided.

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

#53

Post by uni_rule »

TigeriusKirk wrote: post #39
jstx1 wrote: post #3

> One former Tesla engineer, who spoke on the condition of anonymity to candidly describe the matter but was not involved, said Tesla engineers would have trouble capably assessing Twitter’s code. Distributed systems, the large-scale and spread-out network that Twitter is composed of, are not the automaker’s specialty, the person said. > The “idea of Elon being flanked by his Tesla engineers reviewing Twitter code is…

At the moment, my default position on all stories out of Twitter is that they didn't happen unless confirmed officially by Twitter. And the more nonsensical the story, the firmer that belief is for me.

Well it's not like Twitter will ever officially state: yeah they just walzted in here and did a bunch of moves that made absolutely zero sense, it was a shit show.

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

#55

Post by Nicksil »

sidibe wrote: post #43
the_doctah wrote: post #41

Earlier quoted context omitted.

What hubris to think that your system is so complex that other engineers couldn't understand it.

The hubris is thinking Tesla engineers (who are offered worse pay and wlb relative to Twitter) are coding masters of every domain. I won't even snipe at their own software here. It takes a long time to onboard to a big mature infrastructure that is serving hundreds of millions of users for people moving from a similar company, even longer if your day job is whatever Tesla engineers are doing. And that's onboarding, n…

>The hubris is thinking Tesla engineers (who are offered worse pay and wlb relative to Twitter) are coding masters of every domain. I won't even snipe at their own software here.

Who is thinking that?

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

#56

Post by yrgulation »

marstall wrote: post #26

I was thinking the "30-60" day time window may be a somewhat subtle way of catching out engineers who haven't written a thing in that amount of time. that would be one way to identify low-performers. not unproblematic by a long shot, but quick, and probably somewhat effective. and it wouldn't require any deep knowledge of twitter's codebase on the part of the reviewers.

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.

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

#59

Post by generalizations »

whateveracct wrote: post #40
_vertigo wrote: post #6

Earlier quoted context omitted.

From Musk’s POV, a bunch of solid, well-rounded, and experienced engineers you trust might be enough to tell you “this guy is full of shit” when talking to new people. Maybe it’s less about code quality and more about eng quality.

I guarantee Elon is surrounded by yes-men.

That's not how you build a spaceship.
Post reply on HN