Live data from Hacker News

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

washingtonpost.com

921–930 of 1001 posts

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

#921
post #871
post #853

I worked at Facebook and remember what it was like to first face the total complexity of the system. It’s really hard for me to imagine myself working at a company that deals almost exclusively with machine-generated data (as Tesla does) and being assigned to judge a social platform’s engineering qualify in one day . Cars and spaceships on a closed network are fundamentally “clean” compared to having hundreds of mill…

I suspect it’s less a complete review and more an interview of the senior technical manager, to get a sense of whether they are up to par. Do they think about observability, alerting, refactoring, service architecture, etc. reasonably well? Are there issues with how they motivate their teams or when they give them responsibilities? Are timelines challenging but doable? “Code” is most likely “architecture” and “archit…

This. Evaluation always starts at high level then you gradually get lower level until you draw line to delegate tasks.

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

#922

I 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…

Exactly, more code isn't better

Quite. Code is a liability. LOC is an utterly idiotic metric of programmer contribution, as it incentivizes increasing liability, over all sorts of other better contributions like good design, more automation, mentoring, customer obsession, etc.

(And for those arguing that “but the least amount of lines is not necessarily best”, yes, of course, that can obscure logic; the point isn’t to flip the value of LOC as a metric, the point is to not treat it as a good metric).

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

#923

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.

Comments like this makes me lose faith i humanity. If I were a engineer at Twitter, I'd do my absolute best up to the minute I have to leave the premises. Because I would care about the company, my colleagues and most importantly for the >200m people who use Twitter for fun, educational, business and those who depend on it. But it's probably because I'm an old beard, who value being honest and ethical, to be the bett…

I think being "honest and ethical" is at its heart a useful strategy for organizing the collective work of individuals. It's part of the ethos required for building high-trust groups.

Individuals within a group want to understand the terms under which a group operates, and in particular, how to extract their share of value from the group and how to maintain or enhance their extractable share of value.

The more the rules of a group are perceived to be fair, reciprocal and consistently applied, the more members can trust the group and each other. This relieves the participants of significant cognitive and emotional burden, allows longer-term collective action, and reduces transaction costs dramatically.

But I can intellectually understand the value of opportunistic defection strategies that "cheat" the group, extracting both an unfair share of value (as well as some of the "embodied trust value" resulting in an incremental loss of trust across the group).

I have a personal commitment to honest behavior and I actively avoid low-trust friends, groups and choices. Possibly because I find low-trust situations too stressful and too much work, as well as morally horrifying (whatever that means!) I'd like to believe that I'm fundamentally a "good person" but I acknowledge that it might just be that I'm unwilling to leave the local maximum high-trust situation I've self-selected for throughout my life, or I'm afraid of the risks of defector strategies (or I'm just cognitively and emotionally unsuited to them).

Here's where it gets complicated, because organizations change, trust levels change, the signifiers of trustability change, organizations lie, sometimes organizations are specifically operated to trap and exploit high-honor people, and people have very different ideas about what constitutes "fairness" or "exploitation". I find it hard to criticize someone who chooses to use low-trust tactics against a low-trust or deceptive group.

It seems, looking around different cultures and organizations in the world that there is a huge variation in the principles under which groups function. Apparently "low-trust" is a viable option, although I'm supportive of the idea that high-trust brings a competitive advantage both for groups and individuals, and is worth building and sustaining.

I'm horrified that we seem to have reached some kind of tipping point in the west where a critical mass of elites (who already extract enormous value!) have decided they can extract even more value through high-order defection than by building modern and durable foundations of trust.

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

#924
post #853

I worked at Facebook and remember what it was like to first face the total complexity of the system. It’s really hard for me to imagine myself working at a company that deals almost exclusively with machine-generated data (as Tesla does) and being assigned to judge a social platform’s engineering qualify in one day . Cars and spaceships on a closed network are fundamentally “clean” compared to having hundreds of mill…

My guess is this would be a very high level look at their architecture and maybe a closer look as some specific portions. Like you said these systems are so complex that you wouldn't be able to figure out what is even happening in a day. I don't agree that it's to drive feat at Twitter, as just about any engineer will know what I just said. What I think it's about is driving the headlines, "Tesla engineers are doing…

Twitter has been publishing about their architecture and all the updates to it for years and years, and given countless presentations on it. https://blog.twitter.com/engineering/

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

#926
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.

Yes you absolutely can. If there are obvious mistakes that would be caught by linting or review, you can know that the standard isn't high.

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

#927

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.

Comments like this makes me lose faith i humanity. If I were a engineer at Twitter, I'd do my absolute best up to the minute I have to leave the premises. Because I would care about the company, my colleagues and most importantly for the >200m people who use Twitter for fun, educational, business and those who depend on it. But it's probably because I'm an old beard, who value being honest and ethical, to be the bett…

Im not 100% convinced that tanking Twitter is less honest and ethical than continuing to support it… depending on the scope of the context.

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

#928
post #900
post #863

Earlier quoted context omitted.

Yes, software is typically more complex than a laymen would expect once all of the edge cases and layers of legacy code or “guano” are implemented. However, I doubt that these outside developers are expected to understand everything in a single day. There are legitimate questions regarding how certain sections of the Twitter code operate as it relates to censorship, which is a primary reason Elon purchased Twitter. G…

In a typical acquisition this would have taken place under NDA during due diligence, before closing the deal. But Elon waived it. Now he’s apparently trying to find this shadowy “fifth column” of engineering over the weekend so they could be fired before RSUs vest on Tuesday. It sounds completely ridiculous but isn’t entirely implausible since, after all, we’re talking about the same person who committed $44 billion…

> Nobody in Elon-space seems to be bothered that there’s no undo on alienating a social network’s user base.

Where are they going to go? I don’t see journalists like Nikole Hannah-Jones moving their personal brands to Facebook.

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

#929

What code is he reviewing? And why is he reviewing it? There must be millions of lines of code. Also, why bring in Tesla employees? Twitter employees are also his own, they could do they review for him. Just shows how musk feels about Twitter and the people there. Such disrespect.

They are not reviewing code, they are reviewing people. And doing a terrible job at that if it really involves code printouts and short interviews. This is likely a fishing expedition to collect data to disguise layoffs as performance firings. He's not interested in accurately tell if they are capable or not, he's likely just trying to gauge who to "obviously" maintain and get rid of the rest since he already stated that in his view 75% of the company is redundant.

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

#930

I can only imagine how bad this is for morale. Out of the blue code review conducted by an external company means total lack of trust.

Isn't this kind of thing standard for takeovers?

Not like this. Mostly what happens is a constant barrage of meetings where you present projects, roadmaps, timelines to a variety of people/teams. This seems like its focused on individual "evaluation" so its likely a layoff effort.

This was not a takeover by another company tho, which makes the Tesla participation super shady considering is a publicly trading company. Even if they're not participating in this as Tesla employees it would normally be a firing offense and compliance violation for a normal CEO to take people from one company to work on his other private company and allow the name to be publicized.

Post reply on HN