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

541–550 of 1001 posts

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

#541

Post by dagmx »

vlovich123 wrote: post #536
lupire wrote: post #470

Earlier quoted context omitted.

Why would anyone take him seriously when he is making a massive embarrassment of himself on his first day on the job (after doing the same for months leading up to the takeover?) Musk didn't know the bio of the CEO of the company he was buying (who was also former CTO, engineer, Stanford PhD (thesis topic: making decisions under uncertainty), IPhO gold medalist, top tier Indian tech student) and called him a non-tech…

I have failed to source this claim after some searching: > Musk didn't know the bio of the CEO of the company he was buying (who was also former CTO, engineer, Stanford PhD (thesis topic: making decisions under uncertainty), IPhO gold medalist, top tier Indian tech student) and called him a non-technical "manager type" and refused to ask him any technical questions. Is there some news report you’re referencing or som…

Part of the lawsuit

https://twitter.com/techemails/status/1585804674170355712?s=...

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

#542

Post by bandyaboot »

longrod wrote: post #448

I think people are looking at this the wrong way. It's not so much about the code as it is about establishing an authority. Musk takeover is often regarded as banditry and I wouldn't be surprised if the employees didn't take him seriously in the beginning. This is his way of saying, "I don't trust you, I don't know what you have been up to but things are going to be different so better get used to it." Using Tesla en…

This week Musk sure sounded like someone who was a bit concerned over the potential of losing advertising revenue.

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

#543

Post by [deleted] »

vlovich123 wrote: post #536
lupire wrote: post #470

Earlier quoted context omitted.

Why would anyone take him seriously when he is making a massive embarrassment of himself on his first day on the job (after doing the same for months leading up to the takeover?) Musk didn't know the bio of the CEO of the company he was buying (who was also former CTO, engineer, Stanford PhD (thesis topic: making decisions under uncertainty), IPhO gold medalist, top tier Indian tech student) and called him a non-tech…

I have failed to source this claim after some searching: > Musk didn't know the bio of the CEO of the company he was buying (who was also former CTO, engineer, Stanford PhD (thesis topic: making decisions under uncertainty), IPhO gold medalist, top tier Indian tech student) and called him a non-technical "manager type" and refused to ask him any technical questions. Is there some news report you’re referencing or som…

[deleted]

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

#544

Post by golemiprague »

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.

No post body was provided.

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

#545

Post by Areading314 »

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…

Fixing bugs is part of the job. If you care about the product you work on, you have to fix the bugs and not whine about who originally wrote the code.

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

#546

Post by thepasswordis »

lupire wrote: post #470
longrod wrote: post #448

I think people are looking at this the wrong way. It's not so much about the code as it is about establishing an authority. Musk takeover is often regarded as banditry and I wouldn't be surprised if the employees didn't take him seriously in the beginning. This is his way of saying, "I don't trust you, I don't know what you have been up to but things are going to be different so better get used to it." Using Tesla en…

Why would anyone take him seriously when he is making a massive embarrassment of himself on his first day on the job (after doing the same for months leading up to the takeover?) Musk didn't know the bio of the CEO of the company he was buying (who was also former CTO, engineer, Stanford PhD (thesis topic: making decisions under uncertainty), IPhO gold medalist, top tier Indian tech student) and called him a non-tech…

I mean…he does sound like a non engineer manager type.

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

#547

Post by georgeg23 »

HyperSane wrote: post #526
lupire wrote: post #470

Earlier quoted context omitted.

Why would anyone take him seriously when he is making a massive embarrassment of himself on his first day on the job (after doing the same for months leading up to the takeover?) Musk didn't know the bio of the CEO of the company he was buying (who was also former CTO, engineer, Stanford PhD (thesis topic: making decisions under uncertainty), IPhO gold medalist, top tier Indian tech student) and called him a non-tech…

Musk is just constantly revealing himself to be a fool over and over.

His real enterprise is a massive DoD program, which requires Republicans to fund. Twitter helps him with that and curry favors.

Mike is the ringleader but he's only useful when Republicans are in power.

So not as foolish as he seems, but it's unclear his ploys will pay off. https://en.m.wikipedia.org/wiki/Michael_D._Griffin#Career

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

#548

Post by gwbas1c »

longrod wrote: post #448

I think people are looking at this the wrong way. It's not so much about the code as it is about establishing an authority. Musk takeover is often regarded as banditry and I wouldn't be surprised if the employees didn't take him seriously in the beginning. This is his way of saying, "I don't trust you, I don't know what you have been up to but things are going to be different so better get used to it." Using Tesla en…

> I don't think they can get a clear picture by looking at last 30 days of code

I can very quickly spot developers who are mediocre or worse by looking at their last 30 days off code. (As long as it's a language I have decent experience in.)

I suspect he's trying to access the team's technical competence.

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

#549

Post by jiggawatts »

completelylegit wrote: post #346

Once upon a time at Tesla, Elon brought SpaceX staff in to weed out the undesirables. The autopilot team didn’t like being quizzed on basic c/c++ questions and that was the first time almost all of AutoPilot quit. Or so I heard.

If people developing a system that controls two-ton death machines get their panties in a twist about having to demonstrate basic competency in a memory-unsafe language… it’s probably good that they quit.

Airline pilots don’t quit in a huff because they have to demonstrate basic competency annually.

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

#550

Post by jiggawatts »

antipaul wrote: post #150

Working as a coder in a non-tech industry for a multinational, I appreciate that someone so high up cares about something as “rudimentary” as code.

Famously, Bill Gates would review both code and low-level technical architecture decisions of flagship products.

This shouldn’t be the exception, it should be the norm.

I can always tell which company sells products the CEO doesn’t use and has likely never even seen.

Post reply on HN