Slashdot Mirror

← Back to Stories (view on slashdot.org)

Linus' Lessons On Software Dev Management

Posted by Soulskill on from the if-you-want-something-done-right dept.

Esther Schindler writes "In this interview with Steven Vaughan-Nichols, Linus Torvalds shares hard-won wisdom about managing software development projects, including encouraging community involvement, the importance of programming tools, and ensuring the project stays on track. For instance, regarding getting people to contribute to your project, he says, 'If you start off with some "kumba-ya feeling" where you think people from all the world are going to come together to make a better world by working together on your project, you probably won't be going very far.'"

3 of 132 comments (clear)

  1. Re:Kumba ya? by mugurel · · Score: 5, Informative

    Torvalds was always more pragmatic than Stallman. And Stallman is getting more out of touch with reality, not having programmed the last 20 years.

    If you're trying to say Stallman is a weirdo, I agree, but there's no need to insult the good man.

    Besides that, you don't know what you're talking about. His last commit (at the time of writing) to the emacs source repository was less than a month ago:

    http://git.savannah.gnu.org/cgit/emacs.git/log/?qt=committer&q=stallman

  2. Re:Kumba ya? by miffo.swe · · Score: 5, Insightful

    Stallman is more in touch with reality than most people. Imagine where BSD could have been now without the constant rape and pillaging of it? The reason it flunked is purely because of the license and that nobody ever gives anything back to the BSD community.

    Had Linux been based on the BSD license it would never have taken off like it did.

    --
    HTTP/1.1 400
  3. A stable device driver API would help the users by Anonymous Coward · · Score: 5, Insightful

    Breaking the user experience in order to ‘fix’ something is a totally broken concept; you cannot do it. If you break the user experience, you may feel that you have ‘fixed’ something in the code, but if you fixed it by breaking the user, you just violated that second point; you thought the code was more important than the user. Which is not true.”

    Hmm. So this doesn't count everytime the Kernel APIs change and a bunch of device drivers get broken? IMHO it's the users that get hurt by the lack of stable kernel APIs since the original developers are the only people that have the skills, source and tools to make the fix - if they are still interested.