Live data from Hacker News

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

washingtonpost.com

711–720 of 1001 posts

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

#712
post #564

Earlier quoted context omitted.

>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. You are simply paraphrasing exploitation. >but if you see most of his businesses, his expertise is dealing with governments, contracts and policies makers Looks more like brute force and public shaming to me.

I've been thinking about this a lot lately while reading books about leadership I don't know much about Musk or his companies, but I do know that a single person or a small team can often outperform hundreds of people at a big company. I wonder if he's tapped into that somehow in this case If you're doing something you love with a great team that takes care of you, you can easily work 2x as hard for no extra money wi…

This is magical thinking. Eventually those people burn out.

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

#713
post #65

I'd be pissed off if I were a TSLA stock owner. Is Twitter paying Tesla to contract out these employees for their work? Otherwise, it's tons of thousands of dollars Tesla is pissing away on behalf of the CEO's side-hustle.

As an actual TSLA stock owner, I'm ok with this. It's a pretty trivial amount of work in the grand schema of things and it will probably be compensated to Tesla in some way.

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

#714

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 don't think the code review involves counting the lines. A reviewer can distinguish hundreds of lines of boilerplate from a non-trivial few lines change.

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

#715
post #65

I'd be pissed off if I were a TSLA stock owner. Is Twitter paying Tesla to contract out these employees for their work? Otherwise, it's tons of thousands of dollars Tesla is pissing away on behalf of the CEO's side-hustle.

As an actual TSLA stock owner, I'm ok with this. It's a pretty trivial amount of work in the grand schema of things and it will probably be compensated to Tesla in some way.

[deleted]

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

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

In this case, it would be your new boss asking to make a short presentation of your work, and he has trusted software devs who can smell bs a mile away.

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

#717
post #238

Comments are just full of people who want to bring down Musk for the most trivial things without acknowledging the amount of good he has put forth. FYI, I don't own a Tesla or own their stock or own any stock in Musk owned companies. I don't even follow his twitter account.

> without acknowledging the amount of good he has put forth.

and what that would be , exactly? Come on, list the good.

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

#718
post #631

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.

The employees are vesting the cashed out value (at $54.20/share) of whatever stock they were vesting as of when the deal closed. Although SpaceX apparently has vesting stock in a way that keeps the company private. Some of the text messages Elon sent that were published alluded to that.

The company just buys back the shares. It’s essentially a cash bonus.

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

#719

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…

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.

>If you care about the product you work on

I don't care about the products I work on. I don't own the product, I don't work for an NGO willing to change the world and the product would probably won't revolutionize the industry.

The product's only purpose is to make some people rich. And I don't care for it.

What I care about is being paid, learning, advancing my career and not being bored to death while I work.

So I do quality work because of that. I don't enjoy fixing bugs (some people do), so if I can avoid fixing bugs, I'm happier. I also try to ship as least bugs as possible and I test my code before pushing it. The code has to pass an QA cycle so I will fix my bugs if any. But if some bug is coming from production I'd rather pass on it and take on a feature instead.

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

#720

Earlier quoted context omitted.

The text messages that were published as part of the suit to close the acquisition showed Musk discussing "return to office" as a way to naturally trim some of the workforce by having the dissatisfied remote workers quit on their own. My take on the paper printing is that it is a similar strategy to get people to quit by themselves, because they think it's stupid.

The two aren't similar at all. Commute to work = hours lost every day with drastic lifestyle change. Some people even move further away from the office during pandemic. Printing code on paper = 1 minute of work. Paper and ink are paid by company. It is not really that much of a problem. Actually, this is a punishment on the reviewer. No jump to definition and etc. The printing story is fake. I call it now.

Imagine if you printed off your code and ended up with only a few pages of paper you’d fee pretty silly and may quit from embarrassment

Just a thought nothing to back up this claim

Post reply on HN