Live data from Hacker News

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

washingtonpost.com

521–530 of 1001 posts

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

#521

Earlier quoted context omitted.

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

Facebook? The world wide web? Another website we haven’t seen yet? I remember when the only social network was MySpace and then it wasn’t.

facebook doesn’t work in the same way

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

#522
post #455

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…

Only incompetent managers (and executives) think that "authority" is interchangeable with "respect". Fortunately for Musk, incompetence rarely disqualifies billionaires from anything.

Respect really doesn't have a lot to do with it, being a professional at your position does.

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

#523
post #470

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…

Source?

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

#525
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…

>Why would anyone take him seriously [...] Well, they should, he is their boss now.

I think respect is earned, not an entitlement due to someone's ability to buy a company. There are plenty of bad bosses who should not be taken seriously.

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

#526
post #470

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…

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

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

#527
post #455

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…

Only incompetent managers (and executives) think that "authority" is interchangeable with "respect". Fortunately for Musk, incompetence rarely disqualifies billionaires from anything.

It's painfully obvious your disdain for Musk prevents you from making an observation worth taking seriously.

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

#528

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 suspect that not much will change for users. The folks who want to continue tweeting will do so. The folks who do not want to tweet won't. Everything else is office politics.

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

#529

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 are doing is fixing bugs, you are doing yourself a disservice and so is the org in the way they are treating you. Unless you are the original author of that code. When people don't fix their own bugs, they tend to repeat it in other places. When people tend to fix code they didn't write nor have the proper context on why the code was written like that, they tend to turn it into a mess. IMHO, Developers should be writing new code and maintaining their own code. Never reward developers by giving them more new code and stopping them from maintenance.

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

#530

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…

What a ridiculous viewpoint. I spent two days last week to write a single line of code. It cuts the startup time of the app in half with no downsides. I had to make sure it works in all flavors, on all OS builds, benchmark it to show it works, cherry pick it into various release branches, talk to people about it, etc

If you ask me to print my code and defend it in a meeting, I will instead skip the meeting and respond to one of the dozens recruiters who reach out every week in my inbox. You can keep the engineers who wrote the slow code in the first place. I'm sure they'll have thousands of lines of code to print.

It's just a demeaning process meant to assert the dominance of the new owners.

Post reply on HN