Lines of code written, in isolation, is a strange metric to determine if someone keeps their job or not. I simply don't think this was the only metric. People love jumping to conclusions about divisive characters.
If you are writing HelloWorld-webscale daemon from scratch, then counting +lines is probably "ok", but considering some existing large project like Linux (for instance), you would be well off keeping people who has managed to retain functionality while removing lines. Old projects have a tendency to get a lot of old cruft in which tends to stick (chestertons fence and all that) but someone clever enough to rewrite and remove old useless code is a net win for you, so I agree that if you fire some percentage on most-committed-lines you either had a very recent project from scratch or the measurement is stupid.
I'm impressed Torvalds managed to not know what he was referring to (the Twitter firings).
The missing context whenever this comes up is the fact that it was a surprise one off.
If developers have no idea they're going to be graded by lines of code at some random future date that's a much different situation than saying you're going to give bonuses away every month based on how many lines of code were written.
Everyone knows the second is bad, it'll be gamed massively. The first one could be useful though.
And yes doing it as a one off is still problematic and you can think of all kinds of exceptions, but if you think the organization is full of dead weight in general and overhired massively, a crude stack ranking by lines of code is a pretty good metric for figuring out which (e.g.) 50% is the bottom.
> I'm impressed Torvalds managed to not know what he was referring to (the Twitter firings).
I mean, naughty old Mr Car didn't _invent_ this nonsense; IBM was fairly notorious for it in the 80s, say. He's probably the most prominent recent example.
> The first one could be useful though.
How?
> a crude stack ranking by lines of code is a pretty good metric for figuring out which (e.g.) 50% is the bottom.
No. It's really not. For a start, you probably lose basically everyone very senior by that mechanism. But also you lose the troubleshooters.
"How many lines of code did you write in the past <timespan>" is not a good metric but replaced with a more generic "what did you actually _produce_ recently" I can understand the spirit.
Stupid and smart are stupid terms. There are many, many dimensions to intelligence and a lot of tech elite are too "stupid" to not recognize that being a really "smart" at coding doesn't mean they're really "smart" at everything.
I'd guess Elon and Linus's character sheets are more closely aligned on the same dimensions of intelligence than Linus would like to admit.
Much respect to Torvalds, but all available evidence points to the fact that people that stupid (and some even dumber) do in fact work at tech companies.
If only it stopped at taking credit. That's not half as ego gratifying as stamping your vision of the future <cough>cybertruck</cough> on the roads where monstrosities with deadly edges assault our eyes.
Like many people on both political extremes, Linus Torvalds confuses people who disagree with him with people who are stupid.
Elon Musk is the best engineering manager this century.
And a dickhead.
Edit:
Just re-read the story. Going by the quote there, the interviewer lied about what Musk did and the story lies about what Torvalds actually said about him.
> The best engineering manager in terms of getting things done.
Beyond the joke truck thing, his car company hasn't released a new car in almost seven years. Twitter doesn't appear to have done much beyond release a few previously gated features (longer tweets, tweet editing, and the birdwatch/community notes thing were all things they were previously testing) since acquisition.
Lines of code written, in isolation, is a strange metric to determine if someone keeps their job or not. I simply don't think this was the only metric. People love jumping to conclusions about divisive characters.
If you are writing HelloWorld-webscale daemon from scratch, then counting +lines is probably "ok", but considering some existing large project like Linux (for instance), you would be well off keeping people who has managed to retain functionality while removing lines. Old projects have a tendency to get a lot of old cruft in which tends to stick (chestertons fence and all that) but someone clever enough to rewrite and remove old useless code is a net win for you, so I agree that if you fire some percentage on most-committed-lines you either had a very recent project from scratch or the measurement is stupid.
I'm impressed Torvalds managed to not know what he was referring to (the Twitter firings).
The missing context whenever this comes up is the fact that it was a surprise one off.
If developers have no idea they're going to be graded by lines of code at some random future date that's a much different situation than saying you're going to give bonuses away every month based on how many lines of code were written.
Everyone knows the second is bad, it'll be gamed massively. The first one could be useful though.
And yes doing it as a one off is still problematic and you can think of all kinds of exceptions, but if you think the organization is full of dead weight in general and overhired massively, a crude stack ranking by lines of code is a pretty good metric for figuring out which (e.g.) 50% is the bottom.
> I'm impressed Torvalds managed to not know what he was referring to (the Twitter firings).
I mean, naughty old Mr Car didn't _invent_ this nonsense; IBM was fairly notorious for it in the 80s, say. He's probably the most prominent recent example.
> The first one could be useful though.
How?
> a crude stack ranking by lines of code is a pretty good metric for figuring out which (e.g.) 50% is the bottom.
No. It's really not. For a start, you probably lose basically everyone very senior by that mechanism. But also you lose the troubleshooters.
Torvalds talking out of his ass? impossible
For all the criticism about the Twitter downsizing they have managed to keep the service running on a much smaller staff count.
Smaller staff and smaller user base.
Smaller ad customer base, too, and qualitatively less demanding.
if bots count as user base they're thriving
[dead]
"How many lines of code did you write in the past <timespan>" is not a good metric but replaced with a more generic "what did you actually _produce_ recently" I can understand the spirit.
Stupid and smart are stupid terms. There are many, many dimensions to intelligence and a lot of tech elite are too "stupid" to not recognize that being a really "smart" at coding doesn't mean they're really "smart" at everything.
I'd guess Elon and Linus's character sheets are more closely aligned on the same dimensions of intelligence than Linus would like to admit.
Much respect to Torvalds, but all available evidence points to the fact that people that stupid (and some even dumber) do in fact work at tech companies.
Musk is not as intelligent as he claims to be. He is happy to take the credit for others' work.
If only it stopped at taking credit. That's not half as ego gratifying as stamping your vision of the future <cough>cybertruck</cough> on the roads where monstrosities with deadly edges assault our eyes.
We haven't got those cybertrucks over here yet, but yes, they are extremely ugly.
That's just what management does.
> Musk is not as intelligent as he claims to be.
It is a characteristic of those who claim to be intelligent.
> Linus Torvalds recently appeared in a YouTube video hosted by the popular Linus Tech Tips (LTT) channel - run by a 'separate' Linus Sebastian
... Wait, does the author think that they are _actually_ the same person? If not, why the scare quotes?
[dead]
[dead]
Like many people on both political extremes, Linus Torvalds confuses people who disagree with him with people who are stupid.
Elon Musk is the best engineering manager this century. And a dickhead.
Edit: Just re-read the story. Going by the quote there, the interviewer lied about what Musk did and the story lies about what Torvalds actually said about him.
“The richest” !== “The best”.
Okay, to be explicit: The best engineering manager in terms of getting things done.
I have read that Musk was a complete cunt to the people working for him, long before he took over Twitter.
> The best engineering manager in terms of getting things done.
Beyond the joke truck thing, his car company hasn't released a new car in almost seven years. Twitter doesn't appear to have done much beyond release a few previously gated features (longer tweets, tweet editing, and the birdwatch/community notes thing were all things they were previously testing) since acquisition.
Like, I dunno, I'm not seeing it.
> Elon Musk is the best engineering manager this century
Grok, is that you?