Free Newsletters
Technology & Business Daily

InfoWorld
Log-in | Register

  Tuesday, April 08, 2003 

Blogs, scopes, and human routers

Back before there were blogs, my groupthink laboratory was the NNTP protocol, which I used at roughly four levels: workgroup (my new media development team at BYTE Magazine), department (the BYTE editorial team), company (all of BYTE), and world (BYTE's public newsgroups). I learned something then that was, and still is, quite difficult to describe -- but critically important. I call it the principle of scoped collaboration, and I illustrated it in a chapter of my book like so:

The crucial insight, for me, was that a new kind of skill is becoming relevant: the ability to make effective use of overlapping scopes. Here's how I put it then:

If I am seeking or sharing information, why do I need to be able to address a group of 3 (my team), or 300 (my company), or 300,000 (my company's customers), or 300 million (the Usenet)? At each level I encounter a group that is larger and more diffuse. Moving up the ladder I trade off tight affinity with the concerns of my department, or my company, for access to larger hive-minds. But there doesn't really have to be a tradeoff, because these realms aren't mutually exclusive. You can, and often should, operate at many levels. [Practical Internet Groupware]

Today, you can see a great example of this principle of overlapping scopes. Chris Anderson copies some material from his private "work blog" at Microsoft over to his public blog, SimpleGeek, in order to attract outside perspectives into the organization. This is precisely the maneuver that I have found to be powerful, yet elusive to explain. Chris's entry takes a confessional tone. "I don't understand blogging," he writes, and he worries that software will get written before the subtleties sink in. That's a valid concern, and a great issue to raise now that blogware has begun to issue from Redmond. As a matter of fact, though, Chris's take on blogs is spot on:

One reason I believe that blogs are great for corporation internal communication is the question of distribution lists. Inside of Microsoft we live and die by email. However the constant spam of email to large distribution lists ends up drowning out the important information. For many types of communication (but not all) blogs provide a better way of communicating. There are many cases where you as the publisher of a piece of information don't know who would be interested. Blogs are a way to "publish and forget" - you fire the information out there, and interested people will find it. Once I add our internal blog server to the corporate search service, suddenly I could find people that worked on products that I wanted to communicate with. Amazing. [SimpleGeek]

Even more interesting, at least to me, is Chris's instinctive use of overlapping scopes, and his positioning of himself as a router among them. "This is quoted from my internal blog at work..," he writes, "I know that there are much better experts out there to answer this question...I hope some of them can respond." Bing!

 

A conversation with MySQL's Mårten Mickos

Mårten Mickos
Mårten Mickos

As the CEO of MySQL, the company behind the open-source database, MySQL, Mårten Mickos is leading the company's move into the enterprise market against players such as Sybase, Oracle, IBM, and Microsoft. The company recently announced optimization for the Intel Itanium 2 processor running Linux, directed at large databases, data mining, and other enterprise applications. Jon Udell, the InfoWorld Test Center's lead analyst, spoke with Mickos about dual licensing, modular architecture, and the perception vs. the reality of MySQL. [Full story at InfoWorld.com]
I first met Mårten (that's a Unicode U+00E5, LATIN SMALL LETTER A WITH RING ABOVE, HTML entity å) about six years ago. He was working for Solid Technologies, whose database I had chosen for the subscriber version of BYTE.com I was then building. In 1997 the acronym LAMP (Linux/Apache/MySQL/Perl|Python|PHP) had not yet appeared, but you could say it was a LAP project: Linux, Apache, and Perl.

lamp

The notion of building what was for me a mission-critical application on open source foundations was a bit radical, and so I actually prototyped on a dual track: Linux/Apache/Perl and the Solid database versus NT/IIS/Perl and the NT version of Solid. In the end I chose the LAP solution. If I had to make the same choice today, I'm not sure which way I'd jump. My solution depended on Apache's mod_rewrite, a technology that's still not mature in the Windows space. On the other hand, the .NET Framework is very appealing. But here's the real point: LAP has morphed into LAMP, and the landscape of choice is different. A key component which did not then play a prominent role in the open source half of the equation -- the database -- now does.

 


Recent Entries


















































Sponsored Technology Links

 
 
 HOME  NEWS  BLOGS  PODCASTS  VIDEOS  TECHNOLOGIES  TEST CENTER  EVENTS  CAREERS   About | Advertise | Awards | RSS | Contact Us 

Copyright © 2008, Reprints, Permissions, Licensing, IDG Network, Privacy Policy, Terms of Service.
All Rights reserved. InfoWorld is a leading publisher of technology information and product reviews on topics including viruses,
phishing, worms, firewalls, security, servers, storage, networking, wireless, databases, and web services.

CIO :: ComputerWorld :: CSO :: Demo :: GamePro :: Games.net :: IDG Connect :: IDG World Expo
Industry Standard :: IT World :: JavaWorld :: LinuxWorld :: MacUser :: Macworld :: Network World :: PC World :: Playlist