6 ms·

Deceptive title. tl;dr: Linus doesn't read kernel patches anymore, because subsytem maintainers do and just send him a summary. He's been working with them fo

by wisty 14y ago

Deceptive title. tl;dr: Linus doesn't read kernel patches anymore, because subsytem maintainers do and just send him a summary. He's been working with them for about 10 years, so he trusts them. Most of his work on the kernel is sorting out arguments, and making sure things go to the right person.

dkroy 14y ago
Okay, I should have read your post, we wrote the same thing...
derleth 14y ago
> Most of his work on the kernel is sorting out arguments, and making sure things go to the right person. tl;dr for your tl;dr: Linus Torvalds is, in fact, a good manager.
- est 14y ago
  So does this makes GIT an ERP system, for geeks with code?
  - ako 14y ago
    More like MS-project/MS-excel for geeks...
  - arethuza 14y ago
    I would say no unless financial transactions became an integral part of git - which isn't exactly a pleasant thought.
    - sirclueless 14y ago
      I like it: sign off on commits with SHAs of bitcoin transactions to the original developer. "Linus Torvalds gave SirClueless $10.00 for fixing issue #12073"
      - est 14y ago
        The bounty is calculated according to the diff's Levenshtein distance
Zenst 14y ago
I agree about the title, I would of gone with: "How I learned to delegate and realise people were part of the asernal of tools available at my command prompt"
andrewljohnson 14y ago
Deceptive is not the right word. How about attention-grabbing, or excellent, to describe the headline instead? First of all, it's a direct quote from the article. Second, I think some people (like you) object to any attention-grabbing headline, for no reason at all. It was a good article, and that was a good quote to use to get people to click and read. I can't even imagine how terrible Hacker News would be if all the titles were like what one of the people who responded to your comment said: "How I learned to delegate and realise people were part of the asernal of tools available at my command prompt" This is a drab, dull, and terrible headline.
- manaskarekar 14y ago
  > Second, I think some people (like you) object to any attention-grabbing headline, for no reason at all. It was a good article, and that was a good quote to use to get people to click and read. I think that's unfair. If an attention grabbing headline is deceptive but leads to a good article, it's still deceptive.
  - andrewljohnson 14y ago
    But it's not deceptive, it's what Linus said, and I think it gets at a good key idea in the interview - that Linus has transitioned from being primarily a code reviewer to primarily a manager of people. The part about moving to being a manager of people is just not included in the headline - you learn that by clicking the intriguing title.
    - jlgreco 14y ago
      That quote, on it's own, has a very different meaning to readers if it is not accompanied by the rest of the article. That is why it is deceptive. Now, of course you could say that you should read the article and then you would not be left with the wrong impression... but I think few people read the articles of every headline that they see. Nor should they be expected to, our time is all valuable, we can't all do HN 24/7. Certainly you should always read the article before commenting, but as it stands this headline is deceptive to people who plan on doing neither. Nor is it reasonable to expect people to not take away impressions from headlines that they don't plan on investigating further. Even if you decided to do that, it would be near impossible to prevent yourself from making unconscious associations. Headlines should be short, more or less informative, but never deceptive. "Massive PHP bug ...that I almost let through code-review" and "Massive PHP bug" could both be headlines to the same article, but one is deceptive. Unfortunately, it is also the one that is likely to get more hits... Readers who do not particularly find PHP of interest will skip reading either, but the second headline will also (unjustly) form/strengthen a negative association they have with PHP.

by wisty 14y ago

dkroy 14y ago

Okay, I should have read your post, we wrote the same thing...

derleth 14y ago

> Most of his work on the kernel is sorting out arguments, and making sure things go to the right person. tl;dr for your tl;dr: Linus Torvalds is, in fact, a good manager.

est 14y ago
So does this makes GIT an ERP system, for geeks with code?
- ako 14y ago
  More like MS-project/MS-excel for geeks...
- arethuza 14y ago
  I would say no unless financial transactions became an integral part of git - which isn't exactly a pleasant thought.
  - sirclueless 14y ago
    I like it: sign off on commits with SHAs of bitcoin transactions to the original developer. "Linus Torvalds gave SirClueless $10.00 for fixing issue #12073"
    - est 14y ago
      The bounty is calculated according to the diff's Levenshtein distance

Zenst 14y ago

I agree about the title, I would of gone with: "How I learned to delegate and realise people were part of the asernal of tools available at my command prompt"

andrewljohnson 14y ago

Deceptive is not the right word. How about attention-grabbing, or excellent, to describe the headline instead? First of all, it's a direct quote from the article. Second, I think some people (like you) object to any attention-grabbing headline, for no reason at all. It was a good article, and that was a good quote to use to get people to click and read. I can't even imagine how terrible Hacker News would be if all the titles were like what one of the people who responded to your comment said: "How I learned to delegate and realise people were part of the asernal of tools available at my command prompt" This is a drab, dull, and terrible headline.

manaskarekar 14y ago
> Second, I think some people (like you) object to any attention-grabbing headline, for no reason at all. It was a good article, and that was a good quote to use to get people to click and read. I think that's unfair. If an attention grabbing headline is deceptive but leads to a good article, it's still deceptive.
- andrewljohnson 14y ago
  But it's not deceptive, it's what Linus said, and I think it gets at a good key idea in the interview - that Linus has transitioned from being primarily a code reviewer to primarily a manager of people. The part about moving to being a manager of people is just not included in the headline - you learn that by clicking the intriguing title.
  - jlgreco 14y ago
    That quote, on it's own, has a very different meaning to readers if it is not accompanied by the rest of the article. That is why it is deceptive. Now, of course you could say that you should read the article and then you would not be left with the wrong impression... but I think few people read the articles of every headline that they see. Nor should they be expected to, our time is all valuable, we can't all do HN 24/7. Certainly you should always read the article before commenting, but as it stands this headline is deceptive to people who plan on doing neither. Nor is it reasonable to expect people to not take away impressions from headlines that they don't plan on investigating further. Even if you decided to do that, it would be near impossible to prevent yourself from making unconscious associations. Headlines should be short, more or less informative, but never deceptive. "Massive PHP bug ...that I almost let through code-review" and "Massive PHP bug" could both be headlines to the same article, but one is deceptive. Unfortunately, it is also the one that is likely to get more hits... Readers who do not particularly find PHP of interest will skip reading either, but the second headline will also (unjustly) form/strengthen a negative association they have with PHP.