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

831–840 of 1001 posts

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

#831

Post by DoneWithAllThat »

jldugger wrote: post #581
johnnyAghands wrote: post #558

I don't see what the big deal here is. I feel like it's the obvious move. He wants a no nonsense review of the current state of things at Twitter, and isn't wasting time. I'm assuming these engineers he trusts and wants an objective review instead of some bs from folks too removed.

The big deal is that Tesla didnt buy Twitter, Musk did. Based on the Tesla engineers doing due dilligence on a non-Telsa acquisition seems like a conflict of interest.

That isn’t what conflict of interest means. It’s a complete non-sequitur in this context.

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

#832

Post by DoneWithAllThat »

threeseed wrote: post #389
glitchc wrote: post #364

Musk sounds like a nightmare to work for. Why would any self-respecting developer stick around under these conditions? I expect an exodus of talent from Twitter in short order.

Cult of personality. Steve Jobs, Larry Ellison, Bill Gates etc. were all a nightmare to work when they were younger.

Well-behaved men rarely make history.

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

#834

Post by mritchie712 »

lexandstuff wrote: post #326
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.

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 valuable.

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

#835

Post by slapthatchild »

I once reviewed code written by an outsourcing place in India. That is when I realized the difference in quality between the hemispheres. It was riddled with hard coded unescaped SQL strings. Old habits die hard for many of us. Especially if we are here on H1B's.

The client then hired an American .NET shop to recode their flailing PHP code to feel trust and safety with respect to their products offering.

Let's just say I am not surprised at this code check. It is the right thing to do, especially with Twitters performance. They all just got complacent. Happens to all the big and stuffy companies.

Meta also needs a shake up. Bezos should come out of retirement and take the helm from that child who is running it now. Before he sinks the total ship.

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

#836

Post by johneth »

uwuemu wrote: post #770
praptak wrote: post #755

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.

Quoted post unavailable.

An impressively buzzword-laden, almost unhinged comment.

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

#837

Post by tkiolp4 »

segmondy wrote: post #529
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…

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…

Please. If any we, developers, should be removing code. I solve problems. The fewer code I write the better.

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

#838

Post by criley2 »

maximus-decimus wrote: post #693
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…

People leave jobs. If you're working at a company that's decades old, the people who did create the bug might have left the company 20 years ago. I don't know for your job, but at mine code is supposed to stick to teams rather than people, so even if the people didn't leave the company, they probably changed teams and don't own the code anymore.

Hard agree. The only case where "You fix all your own bugs" makes sense is a small company or start-up... but it's also a bad idea. Every engineer should get up to speed on every feature until it is no longer feasible/reasonable to do so.

We intentionally cross-train and work bugs in "others code" (we do not assign code ownership, after I review and it is merged, it's is my code now, for as long as I work here lol).

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

#839

Post by fomine3 »

shantanu77 wrote: post #552

Musk has extraordinary capability of extracting every bit of potential a person can deliver. Either you work crazy at your 200% or you are worthless and the company is not for you. Twitter will see lots of layoffs, massive restructuring - some unknown people being promoted for top roles, but end result will be better financial. I am not sure Twitter will remain the same as it is. Lots of people think Elon is not good…

> Elon is not good at dealing with public perspective or government

Really? I thought opposite. Tesla growth was helped a lot by EV subsidy. SpeceX was made thanks to space industry privatization, and get launching tasks from govt. Boring Company is something like for public transport infrastructure.

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

#840

Post by tkiolp4 »

slapthatchild wrote: post #835

I once reviewed code written by an outsourcing place in India. That is when I realized the difference in quality between the hemispheres. It was riddled with hard coded unescaped SQL strings. Old habits die hard for many of us. Especially if we are here on H1B's. The client then hired an American .NET shop to recode their flailing PHP code to feel trust and safety with respect to their products offering. Let's just s…

I don’t think it’s about the hemispheres, but about outsourcing. The developers I know who work for outsourcing companies are the less skilled devs I know. Also the pay is lower and the conditions are worse. Zero incentives to become better at your job. Working for a product company is a game changer.
Post reply on HN