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

321–330 of 1001 posts

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

#321

Post by voxl »

LouisSayers wrote: post #96
PM_me_your_math wrote: post #27

Didn't Musk get rich solving complex problems? The ink isn't even dry yet and there is a rush to judgement, speculation, and wild assumptions that are simply shameful. How many cars did Tesla sell on the day after his investment?

People always do this with Elon... it doesn't matter if he's making cars, building rockets or taking on social media, the general consensus is that he doesn't know what he's doing and will fail. But, who's the richest man in the room? Who was right and who was wrong? People can hate on Elon all they want, but it's pure ignorance to think that we know any better. Let the man work his magic, I'm curious to see what he…

Being rich has almost nothing to do with your ability, talent, or intelligence. It the single most important factor is luck. This is why you often find CEOs looking down on those with PhDs, because they have an inflated sense of self-worth for being "more rich." When in reality a PhD is a very difficult test of your work ethic and creativity, and being a successful CEO is a matter of luck and connections.

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

#322

Post by inferiorhuman »

fleddr wrote: post #301

I think most are missing that this is a code review + loyalty review. For sure a software engineer from Tesla, or even a manager, can get an idea of how valuable/productive a coder is without fully understanding the code in detail. How many PRs? What does the code do? How was it reviewed? What value does it bring to stakeholders (users, business revenue)? Sure enough this way you can get a rough idea of how much work…

  I think most are missing that this is a code review + loyalty review.
I think most people realize that it's more than a code review, in fact I suspect that it's such a transparent loyalty review is exactly why so many people's feathers got ruffled.

  For sure a software engineer from Tesla, or even a manager, can get an idea of
  how valuable/productive a coder is without fully understanding the code in 
  detail.
Yeah, maybe. But Musk is asking SWEs to print 50 pages of their code so he can personally can review it. Any halfway competent manager or exec should be able to see this is not a good way of reviewing performance in earnest.

https://twitter.com/caseynewton/status/1586127052767318016

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

#323

Post by la64710 »

This is really a drama a publicity stunt , what it really is a deal bankrolled by the right wing / ultra conservative class that is ok with and even desires to put down other human beings based on their race or religion and do it freely without getting banned.Twitter is the battleground where this played out.

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

#325

Post by dmak »

scaramanga wrote: post #296
helf wrote: post #259

Earlier quoted context omitted.

That’s because you can start a buncha stuff that ends up great and still be a raging narcissistic man-child. And a whole lot of people want to just overlook everything because “he makes a lot of money” or “I like this tech thing”

Or buy it off someone else after they start it, and then use them for non-consensual buggery (in the metaphorical sense, since only one of them is blonde enough for Musk's tastes).

This reads off as really salty because of how you are trivializing it.

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

#326

Post by lexandstuff »

braingenious wrote: post #151

All of this is so funny in general. It seems possible that Twitter might go the way of Tumblr in that goofy policy changes alienate the core userbase. I couldn’t imagine betting billions of dollars on a property that could basically just become a valuable-ish domain in the future.

It seems almost inevitable it will go the way of Tumblr, Friendster, Hi5, Bebo, MySpace, Orkut, Google+ and soon Facebook.

Social networks don't have a particularly long life expectancy.

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

#327

Post by sbf501 »

colechristensen wrote: post #305
braingenious wrote: post #151

All of this is so funny in general. It seems possible that Twitter might go the way of Tumblr in that goofy policy changes alienate the core userbase. I couldn’t imagine betting billions of dollars on a property that could basically just become a valuable-ish domain in the future.

Nah, there’s nowhere else for cable news to pull hot takes from social media.

This is the true lifeblood of Twitter.

I think if someone created Twitter for journalists, pundits, wonks, and politicians -ONLY- maybe it would be a place to go? Like something that requires a journalism credential, or a TV host, or an actually office holder title. Sure there'd be crazies, but at least there'd be a source for hot takes.

Twitter could still exist for "citizen journalism", but the two wouldn't mix as heavily.

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

#328

Post by SketchySeaBeast »

throwaway09223 wrote: post #90
aaronharnly wrote: post #18

Earlier quoted context omitted.

Respectfully, very little of this seems to be operating by standard procedure. Have you seen the incoming CEO ask people to bring printouts of their code, ever?

Musk is reportedly looking to cut deadweight before Nov 1st when equity vests -- with layoffs possibly happening over the weekend. He might already have a basic idea of key teams and for non-key teams he might be looking to cut very fast. I absolutely have done things like this when acquiring companies - sat with people, asked them to basically interview for their own jobs while showing me the most important thing th…

> asked them to basically interview for their own jobs while showing me the most important thing they wrote in the last quarter

This is builds the same dysfunctional system's that causing so many problems for Google - the people maintaining the vital systems won't have anything cool to show, but they will be the ones that made sure the bills kept getting paid.

> I can see why it might make sense to just tell people to print stuff out to demonstrate competency

All they are demonstrating their is their ability to sell themselves.

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

#329

Post by ozzythecat »

I’m honestly baffled with the obsession with Musk. Many folks here seem to despise him. But we can’t stop obsessing with the guy. At this point, to me it feels like envy. Musk, despite however he is as a person, is wildly successfully across several verticals. Rather than being a suit and tie corporate person, he literally posts memes, and has a IDGAF attitude. Does he owe this crowd anything? Twitter and its board moved forward with this deal, no? Are we surprised Musk is being Mush?

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

#330

Post by alchemist1e9 »

8192kjshad09- wrote: post #287
alchemist1e9 wrote: post #253

Earlier quoted context omitted.

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.

This was just over 600k of mostly c++ code. It’s certainly true that it helped I was familiar with the domain and the various technologies they had used, like CORBA and xml, this was late 90s.

10M is a pretty massive codebase like the entire linux kernel with all drivers is somewhere in that size. Most corporate systems aren’t that big and even for Linux you wouldn’t need to understand all drivers to understand the core kernel, I suspect the core kernel is maybe max 1M.

Post reply on HN