You ain’t seen nothing yet

Visualisation tools are going to become more and more important over time, as we struggle with problems like “information overload”, problems that have been with us so long they’ve become cliches.

Statistics are made to lie. The lies stick because Innumeracy is rife. Despite everything that John Allen Paulos has done. And Powerpoint, usually bad Powerpoint, rules over all. What makes the innumeracy unbearable is the fact that poor visualisation techniques are then used to propagate the lies.

A sorry state of affairs? Well, that’s why I found this representation of visualisation methods uplifting.

Don’t just look at the table. Run your cursor over it. Move it from element to element. See what can be done. We need ontologies and topologies like this one to help us work out what to do. Thanks to Cory for the find.

As if I need an excuse to mention the BTO track.

Musing about opensource: The threat is stronger than the move

What do you do when you’re told to take it very easy, when you’re told to make “slow” a polysyllabic word? If you’re me, and you also have a deep-seated protestant work ethic in you, you struggle. Big time.

Well, that’s what I did for a little while last month, struggling to get past the denial stage. I really didn’t know how to do nothing. Then, come the new year, I had a Road To Damascus experience and then I settled down into an easy rhythm of eat-read-sleep-potter-about-aimlessly, interspersed with the real joy of spending time with my wife and kids. While on the subject of convalescence, my thanks to all who sent me get-well-soon messages. As you can see the messages are working…

Now to the point of this post.

As part of the pottering-about-reading-aimlessly time, I came across this post by James McGovern, whose blog I get to reasonably often.

Read the post, it’s worth it. James commented on a perception held by some developers that many opensource communities aren’t particularly welcoming, and that developers are put off joining as a result.
And it made me wonder.

I’ve always believed in a community participation rule of thumb, something I’ve written about before here and here. The numbers tell the story:

  • For every 1000 people who join a community:
  • 920 are lurkers, passive observers
  • 60 are watchers, active observers capable and willing to kibitz
  • 15 are activists, actually doing something
  • …and 5 are hyperactive, passionate about what they’re doing, almost to a point of obsession

And this is what I was musing about.

Does it really matter, the number of people who actively contribute to an opensource project? Is there something about the way opensource communities work, something that will always ensure that a very small number are the hyperactive core?

The more I think about it, the more I believe that there’s something important here. Linus’s Law is about eyeballs, not hands, and it’s for a reason:

  • At the heart of every successful opensource community is a small cottage industry. And it is this cottage-industry mindset that makes the community different from other “commercial” ones.
  • The core doesn’t have to scale. The core needs to behave in such a way that Linus’s eyeballs are attracted, and this is done by upholding the right values.
  • Jerry Garcia and gang only needed to make sure that Grateful Dead concerts had “taping rows”; the number of people who sat in them was not relevant (although they were full). In a weird kind of way, the core is the band. The tapers are the activists. The kibitzers are the roadies and volunteers.
  • Together with the audience, they formed a whole and vibrant community.
  • Not everyone needs to be on stage for the community to work. In fact there isn’t space.

It is the freedom of access, represented by the taping rows, that really matters. That’s what makes opensource opensource.

Or, to take a chess analogy:

The threat is stronger than the move.