Category Archives: open source

Stallman and Gates!

Interviewer: Is studying computer science the best way to prepare to be a programmer?

Gates: No, the best way to prepare is to write programs, and to study great programs that other people have written. In my case, I went to the garbage cans at the Computer Science Center and I fished out listings of their operating systems.

You’ve got to be willing to read other people’s code, and then write your own, then have other people review your code. You’ve got to want to be in this incredible feedback loop where you get the world-class people to tell you what you’re doing wrong.

This wonderful snippet was revealed by Dan Bricklin and found in the old book Programmers at Work. Spread the news.

Talent Scrapping

I’m fascinated by the universe of systems that capture a little value from a very large number of people and then aggregate that into something of high value. The list of such systems is huge, just for example:

Here’s a fun little idea I had today along these lines. There is a general classification problem about dialogs. For example say you wanted a classifier for angry dialogs. How could you get such a thing?

Well you could create a Bayesian filter and let a large population of volunteers train it to do the classification. This is the pattern above of a large number of contributors summing up into an aggregated thing of value. In this case the thing of value is a classifier that can recognize a class of text or dialog.

For example here we have a guy who hand built a system to entrap child molesters in online forums by posing as a child. I suspect it would be easy to build a classifier that could monitor dialogs in such chat rooms that did the same thing, and it wouldn’t be hard to find the transcripts to train it with.

It would be very interesting to try this on the messages in a mailing list creating a set of classifiers for various kinds of speech acts: baiting, constructive, helpful, query, answer, discussion, debate, argument, etc. etc. I bet that the spooks have such systems but I wonder how they built them.

I keep trying to find a good name for this class of systems. Brain Farming? Talent Scraping? Help Hoarding?

Smoking Factories of Innovation

I have to put up with a lot of talk about of how to create organizations that generate innovation. Smoke bellowing factories of innovation fed by train loads of recently clearcut ideas.

So I liked these two quotes that crossed my screen yesterday.

“Great ideas, it has been said, come into the world as gently as doves. Perhaps then, if we listen attentively, we shall hear amid the uproar of empires and nations, a faint flutter of wings, a gentle stirring of life and hope. Some will say that this hope lies in a nation; others in a man. I believe rather that it is awakened, revived, nourished by millions of solitary individuals whose deeds and works every day negate frontiers and the crudest implications of history. As a result, there shines forth fleetingly the ever-threatened truth that each and every man, on the foundation of his own sufferings and joys, builds for all.” ~ Albert Camus

and this one too, which though from an entirely different context strikes me as one of the things that makes open source work.

“No missed deadlines, only missed opportunities.”

Well, gotta run.

Tom Sawyer

tomsawyerbythefence.jpg

I may have to start refering to certain business models as “The Tom Sawyer Business Model.” Refering to Tim O’Reilly:

“Quinn nails it. Tom Sawyer with a network connection and a conference budget. (Hat tip to Cory.)” — Tim Oren

So what did Quinn write?

…”if tim really wanted a jet car, he’d throw a conference, invite some jet car enthusiasts and talk about how great it would be to have a jet car and then sit back and wait for someone to build him a jet car. it’s like the peter lynch investing philosophy in reverse: instead of investing in the things you use everyday, get other people to invest in the things you wish you had everyday.” … “you know what makes your conferences good, tim? we all act like 13 year olds. show me, make me care, and when you do, i’ll care so much, and i’ll believe that i can revolutionize the field.” …

The story I assume Tim’s refering to is well worth reading in the original (this web thing is pretty cool ain’t it?). Mark Twain was a genius, but also an enthusiast of the last golden age and lost his shirt as a venture capitalist.

I once listened to the head of Microsoft’s open source program opine that developers “Just want to have fun.” At which point you really need to go listen to Blondie’s “Girls just want to have fun”, but record companies are hording that so I can’t point you to the mp3. My thought at the time was – golly the subtext of developers as girls is like totally on message dude.

But yes, there are a slew of buisness models that work by creating a surface were contributors rondevous and leave behind value. Fly paper if you will.

Open source is one of these. The wise open source operative spends a lot of time mimicing the Tom Sawyer role model. But unlike some pseudo open communities, we at least we carefully craft a license that makes it clear that your contributions remain part of the common wealth.

It’s a trust thing. “Innocence lost” and all that.

Revealing$

Here is an article that I find quite amusing about the free revealing question. Putting on their rational-man everything is a market thinking cap these researchers tackled the privacy problem. They ran a little experiment to see at what price points people would be willing to reveal

For example here’s a little table showing what percentage of their respondents demanded more than $100.00 to reveal the information mentioned:

Percentage Information
48.% Salary
38.% Savings
36.% Spousal Salary
24.% Credit Rating
5.4% Weight
3.5% Age

The article has this great title: “Privacy and Deviance.” That pleasing title arises out their not too surprising discovery that if the respondent percieves the information he is being asked to reveal as being highy deviant compaired to the median he will demand a higher price; particularly if the value would imply a social negative. Overall it’s an fun bit of research. I just love that little be about revealing the spousal sallary.

voice of a group blog

LineDancing.jpg
I’ve never been to a rave and I don’t really want to but I saw one in that horrible movie. Who’s in charge? It is a question that comes up.

When people ask that about open source I like to tease them. I say it’s kind of like what happens if you put a bunch of people together in any group. Pretty soon they all start spontanously dressing a like, using the same cliches, making fun of people outside. It’s in the nature of things, like the rythmic clapping of an audience. I gather that rythmic clapping is somewhat more common in European audiences than American ones.

Standard behaviors can emerge entirely bottom up. Fact is, given the way that power-law network tend to emerge out of all kinds of unregulated linking up, I’m beginning to think it’s more the rule than the exception.

It’s actually kind of amazing the way a lot of open source projects seem to
spontaneously organize. You create a body of code; you add a half a dozen interested parties; after a bit they all start rattling around in something that approaches – just a bit – a synchronized manner. Who’s in charge? The code repository?

In the fractal nature of these kinds of discussions I got to noticing this at three scales all at the same time. First you have the ongoing to-and-fro-ing about “what is a blog.” Which is of course the conversation about what is the emerging standard blog. Second you have the question as it applies to an indivdual and his blog. There you might call it “finding your voice.” Some people’s voice is long tedious essays; others are tightly written humorous observations; some like to write little provocative Zen koans; while yet others have found a voice that consists of just revealing a stream of URLs they find interesting. Part of the tension in the “what is a blog” conversation arises from the way it does the violence of catagorization to individual voices. Who in charge? Where to you get off announcing that the annual christmas letter isn’t a form of blogging.

Group blogs are an fun kind of intermediate level. It’s the middle class! Sometimes easy going, tollerant, urban. Sometimes uptight, gated community, suburban. I’d not noticed the way that if you look at a few group blogs; like many-to-many or crooked timber you can clearly see that the particpants have begun to adopt a similar voice. Comming to them fresh you might assume that they gathered together because they shared a common voice; but if you read some of their individual writing from years past you notice that they had either wider ranges or even entirely different centers of mass. I suspect if you just measured the size of the postings you’s see a kind of learning to clap in unison begins to emerge.

Over on the brand spanking new Planet Apache this process is particularly stark. First off we have a mess-o-people posting how have already developed a voice over the last few years. Second we are aggregating those entirely automaticly from their individual blogs; so to first order there is no reason to expect these voices to begin to standardize. Third the Apache communities I’ve particpated in have been particularly good at remaining both tolerant and diverse – which would suggest there is less social pressure toward a common voice. It’s very much in the best interest of a healthy open source project to remain like that; otherwise you make it a lot harder to bring on new blood. But then on the otherhand the Apache communities I’ve particpated in have been extremely narrowly focused, very much communities of limited liablity. That’s because they focus down onto the working code; often have no other scope. That suggests two things; that these folks have a strong expectation that planet apache will focus down on something, probably the work of the various projects, and secondly that these folks aren’t fluent in what happens if you don’t limit the liablity.

I have good friend who drew my attention to a behavior he calls “monkey see monkey do;” i.e. that we primates like to try things. We watch the other monkeys and then we go “Oh, that looks like fun. I think I’ll try that!” And, it is fun. I certainly tried blogging for much those same reasons.

It will be interesting to see what happens at planet apache. Maybe we will wander into a common voice there. Maybe we will remain “just a bunch a guys.” Maybe some people will choose to submit a partial feed of their own blog not because there are guidelines for the planet’s content but because they decide they want to avoid the subtle temptation to conform any conventions that might begin to emerge there. Certainly some people like to settle into a framework. Who knows?

Hopefully we won’t be tempted to answer the question: “Who’s in charge!” Or was Mark Slemko once so wisely said: “That would be wrong, except when it’s not.”

Open Source, Firms, and Standards

I’ve learned that when people ask me in a puzzled manner “How’s that work?” regarding open source I shouldn’t answer until I’ve let them reveal what aspect of the enterprise bewilders them. For example I had one SVP who’s key question was “How do you get along?” I had a guy who’s primary interest was how do we solve the distribution, or as he put it shipping, problem. After collecting a few dozen of these I’ve come to think it’s a little odd that people assume the greatest mystery about open source is the revealing secrets, or the ip rights issue, or the volunteerism.

The dynamics of open source at the level of firms is particularly interesting to me since it bleeds into another area I’m curious about. How do standards emerge, particularly industrial exchange standards?

The simple model for that stuff is that buyers and sellers rendezvous in markets and since standards make that easier there are network effects which will accelerate the adoption of a few standards. It is simpler if we all use the same weights and measures and it is safer drive on the smae side of the road.

Buyers, sellers, market makers (and their agents) that can consolidate enough power to push standards to emerge will do so. The realist will point out at this point those with that power will advocate choices that benefit them and possible disadvantage than the other players.

In the absence of extreme market power the player will find it advantagous to negotiate a standard and advocate it’s adoption by all parties. Both stages are key, in fact you really have to solve three problems. You have to find representatives of all parties that can bring the right talents to bear on the design problem. You have to muddle thru all the negotiation and coordination problems of getting the standard designed, implemented, and maintained. Finally you have have to solve the advocacy, adoption, distribution, customer support problems.

The good news is that we have a carrot and a stick to make this happen. The carrot is improved exchange efficency, in many cases exchanges become possible that were otherwise impossible. The stick is the fear that other players will abuse their market power to create standards that disadvantage us.

Open source provides a reasonably good framework for working on these problems. The Internet makes it a lot easier to find talent, in particular it gives you a huge sample space draw from and then and makes it easier for the talent to volunteer (no travel!). We have stumbled on some tricks for solving the coordination problem. Optimistic concurrency for example. The net also makes it easier to solve the propagation problem as do the open source licenses/pricing. Working with information goods in an age of vastly increasing communication makes all this a possible.

Any firm involved in any exchange need to think about this. For example if your one of a thousand firms processing phone bills you can a) build it yourself, b) buy it from a vendor, or c) join/create an open source project to do it. Which one is best isn’t obvious. There is a lot of risk in building it yourself. There is the danger of becoming locked into a vendor if you decide to buy it. Coordinating an open source project, or any standards setting exercise, is a huge pain.

If you think of the problem as a game with moves it gets even more interesting. Assume, for example, you have built the solution yourself. In that situation you might find it advantageous to open source it first. It could reduce your development costs. It could force vendors to lower their prices. It could help to assure the industry “does it your way” instead of some other way that would be costly to switch to.

If your a vendor of such software you might want to move toward a more open version of the software for different reasons. If your customers are afraid of lock in this addresses their pain point. If you competitor goes first you could be toast as they become the default answer to the problem. If your customers start improving the software you can capture the value they create.

While open source or standards are dominate strategies in lots of information markets they doesn’t win all the time because the problems (talent, coordination, adoption) are still hard. We are getting better at all three though. It’s only just getting started.

Free Revealing

revealing.jpg

The image on the right is a fragment from an ad that  O’Reilly  runs.

One of the reasons you want smart friends is that they can put a bee in your bonnet that  gets  stuck there for a long time.

Eric von Hippel has done that to me at least twice now. First asking how Open Source solves the coordination problem, and second asking why Open Source developers “freely reveal” (their innovations).

Of course what the bees do once they are in my head is entirely out of the control of the friends that stick them in there.

So I’ve begun making a list that attempts to accumulate why people do and don’t reveal. Why does the young woman reveal her belly button? Why does the coworker say “How’s it going?” It’s a very amusing topic.

Here are just a few reasons why people don’t reveal.

  • Fear of  embarrassment, or reputation damage. “Familiarity  breeds  contempt.”
  • Fear of gaining a reputation as having loose lips.
  • Fear of seeming weak or desperate as you reveal and those around you don’t.
  • Fear of seeming  naive  and child like exhibiting  unwarranted  trust in others.
  • Fear of appear to be a gossip, and hence a member of a social clique of similar people.
  • Fear that you’ll hurt others
  • Fear that you might reveal what is a valuable secret to another in your one of your communities and hence be shunned by that community.
  • Fear of loosing the trade secret advantages the knowledge enables.
  • Confusion that ideas are like physical property – if you give away an apple you can’t eat it.
  • Cost of translating the ideas into something your audience will understand.
  • Cost of finding an audience, i.e. distribution costs
  • Fear that revealing will create a “relationship” you have to maintain over time.

After a while it’s not clear why anybody would reveal anything.  This helps to explain people’s  bewilderment when they encounter free revealing on the net, for example blogging or open source.  The blogging case is particularly curious since the audience you reach is large so the chance of one of those risks kicking off is higher.

But, as my son pointed out, all these reasons have their inverse that can be framed as a positive.

Demand for Features

Clay Shirky writes:

(I remember, a decade or so ago, someone asking on a newsgroup  “How do I post to all the soc. groups at once? soc.* doesn’t seem to work – surely I don’t have to enter all the group names in _by hand!”)

What a delightful example of something I’ve been thinking about recently about how inside of community membranes, where trust exists, queries over the community become more approprate.

The rest of Clay’s posting, about how open enables increased innovation while the capture of that innovation is an orthagonal issue is the tip of a big iceberg!

I learned in Cornes & Sandlers very academic text on public and club goods that there are two interesting edge cases in managing the boundary of a club that can be characterized as how the membrane filters it’s inputs – does it take the maximum or the minimum over the inputs?

Consider the example of trying to find the cure for cancer, a clear example of innovation. In that scenario we want a lot of people searching for the cure, but all we need is for one person to find that cure. In this case the club searching for the cure wants to be maximially open, it wants to filter out the maximal or best cure.

Now consider the example of the club that trying to maintain the leeve along a river. Each property owner along the river contributes to the effort; but the quality of the effort overall is decided by the minimum contribution. In this case (a safety example?) the club’s quality is defined by the minimum over the contributions.

That insight was one of the reasons I became very attracted to the club good cartoon of open source. Open source projects need both. Consider Apache’s HTTPD. It’s like the levee in that any flaw creates a security hole that allows hackers to pour in. It’s like a cure for cancer in that we never know where on the planet some web master might create the next delightful and useful innovation. So the club boundary around the server project has to manage to both maximize the innovative contributions and minimize the bogus ones.

Locusts

ApacheCon is like being a field of locusts. You can almost hear the swarm of
chewing away at the future. There is no buisness model, no project plan, no marketing campaign. Just a hordes and hordes of dudes (though interestingly this year there were substantially more women than last) going – “Hum, I wonder what might happen if I hacked this thing together with that thing… cool, that makes me smile, that was neat.” over and over again. These are the people that take pens apart, that put light bulbs inside of other things just because they can.

Doc Searls gave a very nice talk at ApacheCon. Doc obviously has spent much of his life helping firms figure out how to tell their story so that it will go down the gullet of the media machine reasonably smoothly. Like everybody else he’s noticing that bottleneck like so many others is suffering a firestorm of disintermediation.

So on the one hand you could see him seeking a way to frame the story of what is going on here (what is the story of this open source thing) into the frameworks that his craft knows will make it an appetizing dish to place out on the buffet table where that the passing journalists will heap a helping onto their plate. One part hero. One problem, preferably dress in a war metaphore. A respoution – presumably open source. While on the hand noticing that that question is becoming increasingly uninteresting.

On the otherhand you could see he was in the midst of the puzzling out what would rise from those ashes. It was this puzzling that was delightful to observe because he is a very smart guy and he knows all the current memes with a degree of insight that’s rare. So it was just a joy to watch him reach into his bag of memes and pull one out and turn it over in his hands, say something wise about how it does or doesn’t fit what he was observing in the conference and then set it down, respectfully, and pull out another one.

For example he drew out the blogging meme. He had a wonderful slide where screen snapshots of dozens of blogs written by folks in his audience (a nice touch that) piled up on the screen. A pretty way to show the disintermediation of the traditional media. A compeling way to make clear that even the question “what is the story” is just possibly the wrong question when it’s clear that hundreds of voices are now all speaking at once telling what ever random story they might happen to want to tell.

I guess the blogs reflect that some of the locust’s are mumbling outloud as they chew.

He touched on the DYI IT meme. The end-to-end meme and it’s friend disintermediation and the many volunteers standing by offering to become the intermediary. He touched on the IP enclosure movement meme. etc. etc.

A very nice talk and in a way a very ironic one because Open Source has an undercurrent of shifting power from marketing to engineering, from the PR department alway back to the technologists in R&D. No. Not to R&D; further toward the technologists in the field.

So Doc’s presence, the PR marketing maven, in this crowd has a curious irony to it. It’s as if just as they were loading the Golgafrincham’s B-ship a few of the wisest and cleverest passengers paused and wandered back into the crowd. Thinking as they went: “My, this needs some more thought; something odd going on here.” I’m glad he came.