How "Throwing One Away" Makes Open Source Better

There's a wonderful line in Fred Brooks' book "The Mythical Man-Month", where he says that when writing a program, plan to throw one way - you will anyway. But that's a bit of a problem for conventional software development, because it's not clear when the best time is to throw that one away.

On Open Enterprise blog.

Open Source: A Question of Evolution

I met Matt Ridley once, when he was at The Economist, and I wrote a piece for him (I didn't repeat the experience because their fees at the time were extraordinarily ungenerous). He was certainly a pleasant chap in person, but I have rather mixed feelings about his work.

His early book "Genome" is brilliant - a clever promenade through our chromosomes, using the DNA and its features as a framework on which to hang various fascinating facts and figures. His latest work, alas, seems to have gone completely off the rails, as this take-down by George Monbiot indicates.

Despite that, Ridley is still capable of some valuable insights. Here's a section from a recent essay in the Wall Street Journal, called "Humans: Why They Triumphed":

the sophistication of the modern world lies not in individual intelligence or imagination. It is a collective enterprise. Nobody—literally nobody—knows how to make the pencil on my desk (as the economist Leonard Read once pointed out), let alone the computer on which I am writing. The knowledge of how to design, mine, fell, extract, synthesize, combine, manufacture and market these things is fragmented among thousands, sometimes millions of heads. Once human progress started, it was no longer limited by the size of human brains. Intelligence became collective and cumulative.

In the modern world, innovation is a collective enterprise that relies on exchange. As Brian Arthur argues in his book "The Nature of Technology," nearly all technologies are combinations of other technologies and new ideas come from swapping things and thoughts.

This is, of course, a perfect description of the open source methodology: re-using and building on what has gone before, combining the collective intelligence of thousands of hackers around the world through a culture of sharing. Ridley's comment is another indication of why anything else just hasn't made the evolutionary jump.

Follow me @glynmoody on Twitter or identi.ca.

Why Open Source Will Triumph

This is why the traditional software development model is doomed:

Recently, I wrote a review of the note-taking application Tomboy. Though I find Tomboy exceptionally useful, I had a minor issue with the inability to create new notebooks from within a note. Within hours of the review appearing on Linux.com, Boyd Timothy, one of the app's developers mentioned in the article's comments that my idea had merit and said he would add the feature to an upcoming build. True to his word, he did. This is a shining example of one of the most valued yet sometimes overlooked features of open source software: it really is for the people, by the people.