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

951–960 of 1001 posts

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

#951

Post by seydor »

TheChaplain wrote: post #783
Tiktaalik wrote: post #46

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…

what kind of information is in twitter that does not exist elsewhere? i never remember searching for something and ending up to find the answer in twitter

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

#952

Post by HWR_14 »

pavlov wrote: post #900
cudgy wrote: 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…

> the same person who committed $44 billion without due diligence.

Honestly, I'm not sure what due diligence you think he should have, or could have, negotiated. The code obviously works. The userbase is there. They are public, so a lot of information is known.

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

#953

Post by [deleted] »

tasty_freeze wrote: post #203

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…

[deleted]

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

#954

Post by dralley »

mritchie712 wrote: post #834
lexandstuff wrote: post #326

Earlier quoted context omitted.

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.

inevitable? there are some pretty simple things they could do to double revenue: 1. allow people to pay for a blue check to be verified 2. make "twitter blue" actually valuable (e.g. detailed analytics on your followers, tools for composing threads, actually monetizing revue) 3. payments and clearly by this article, they are looking to reduce costs. Double revenue and halve costs and you have something pretty valuabl…

I'm so pissed that Scroll died for "Twitter Blue"

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

#955

Post by mlonkibjuyhv »

makeitdouble wrote: post #810
segmondy wrote: post #529

Earlier quoted context omitted.

I once reviewed code for a company that got purchased. I took less than a few hours to reach conclusion. There were 7 developers and in 2 months only one was writing code. The entire team but that one developer was fired. Twitter has grown a reputation for being slow and a rest and vest haven. Won't be surprised if they are looking for people not writing code. On a different note, If you're in a large org and all you…

＞ There were 7 developers and in 2 months only one was writing code. I would suppose you were looking at many more signs and metric, but then you say it only took you a few hours, so perhaps not ? I’d assume that dev wasn’t actually writing alone, and people had to discuss the design, talk with the PO/stakeholder, review the code, eventually QA it, manage the deployments etc. Perhaps that poor soul was doing everythi…

This is probably an extreme example, but it is no secret that the majority of people employed in an organization actually does barely anything of value. Price's law comes to mind.

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

#956

Post by pessimizer »

manuelabeledo wrote: post #869
aliqot wrote: post #868

Earlier quoted context omitted.

> drive fear at Twitter Auditing what you just bought is about as smart as taking the used car you just bought to the shop to get everything checked over and tightened and lubricated.

Right. But smart people would take a mechanic with them before buying the car. A meaningful audit at Twitter would take months. This is but a stunt.

You have to remember that he didn't want to buy the car at all.

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

#957

Post by sangnoir »

cudgy wrote: post #863
pavlov wrote: 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…

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…

> Given the activist mentality (and possibly hostile to new ownership) of a certain number of developers, it seems perhaps prudent to analyze the code and evaluate the existing developers immediately upon purchase of the company.

Checking the code doesn't make sense, unless you think Twitter is some rinky-dink outfit[1]. If they want to inspect foe activism, they should check the configurations - not code. The engineers only add the knobs and dashboards[1], an entirely different team takes care of operations.

1. Based on what I've gleaned from similar-sized tech companies, or even those 2 orders of magnitude smaller.

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

#958

Post by smrtinsert »

aliqot wrote: post #868
pavlov wrote: 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…

> drive fear at Twitter Auditing what you just bought is about as smart as taking the used car you just bought to the shop to get everything checked over and tightened and lubricated.

It's not the right people so it's not an audit

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

#960

Post by blindriver »

kalabilla wrote: post #604
blindriver wrote: post #603

Earlier quoted context omitted.

Twitter is a private company now. There are no more stocks to vest, so the idea that this is to dodge vesting schedules doesn't make any sense whatsoever.

Private companies have stocks. They are just on traded on exchange

Not Twitter. They all got bought on Friday by Elon. There's no way they would have time to create the necessary legal structure by Tuesday to be able to allocate shares and even to give them to employees.
Post reply on HN