Ward's Wiki

Recently doing research into Wiki's, I've gained a renewed appreciation for the discussion that went on (and still goes on somewhat...) in Ward Cunningham's original Wiki dedicated to pattern discussions. Topics are organized by topic using Wiki words, and there is usually a vibrant discussion that goes on in the page. These discussions are sort of hard to follow since the wiki doesn't have built-in support for discussion threading. On the other hand, discussions are expected to be refactored into the body of the topic's documented by the community. Wikipedia refines this concept a bit by having a talk page behind every document (they are separate but connected).

LtU on the other hand, is more like a newsgroup: you can post a forum topic, but the body of the topic is rarely edited (if only to make corrections) after the topic is started. The discussion is not re-factored into the body of the topic, while some topics are repeatedly revived in slightly different ways and cannot be consolidated into one discussion because refactoring isn't supported. Some topics act kind of like articles, but content is necessarily added as comments since only the owner of the topic can edit the body.

So what's my point? Obviously Ward's wiki is not as popular as it used to be, while LtU is a growing community. Is this because what people actually want are forums and not wiki's? I see a lot of value in the wiki approach myself, and would like my so-called cake and eat it to (that is to say wiki topics with threaded discussions and refactoring).

Anyways just a thought.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Hack value

Is WardsWiki the best hack ever? The impact per line of code is unbelievable.

TiddlyWiki is even hackier

Who would think to build a wiki out of a single web page, make it support plug-ins, etc.? It's the original hack carried through to perfection.

I currently use this to manage a bunch of things.

Fun fact: Ward was actually embarassed by how simple his wiki was at first, until everyone really said they loved it.

I've always found that wiki

I've always found that wiki hard to follow. LtU discussion threads have a more rigorous, linear progression, which I find very easy to follow and results in good retention. Particularly if you're new to this stuff, the progression from what at first seems like a sensible idea, to why it runs into problems leading into the final solution is instructive.

Hard-to-follow discussion

Hard-to-follow discussion

I think the thing that makes Ward's Wiki hard to follow is lack of a good delta system, as well as the ability to show who said what. I often can't tell where one person's views ends and another person's views begin.

I don't think you need overly structured "conversations" metaphor as a solution. That's just injecting process as a way to institute bureaucracy.

At work, we were actually using Etherpad instead of Google Wave, despite the fact all developers got early versions of the Wave Beta. Wave is just waaaay too structured for our needs. Etherpad gives us freeform editing and allows us to collaborate in real-time. I really think Google Wave is overkill for most people. But Etherpad uses text highlighting to show you who said what. Sure, somebody can always erase and re-state what somebody else said, but it is almost always obvious that it is merely an editorial pen. Likewise, StackOverflow allows editorial pen features and things are still fairly rigorous.

Etherpad doesn't have a linear progression. Instead, it has a more literate progression! Why you would want linear progression or threaded progression is beyond me. The Spirit of Google Wave, and by reduction LtU, is that people own chunks of texts. For an encyclopedia or even a codebase, this is a bad model.

Blending of Viewpoints...

I often can't tell where one person's views ends and another person's views begin.

One man's feature is another man's bug, eh?

Context

When two sides are clearly having a discussion, and then a third party appears to jump in, it gets confusing, especially with anonymous comments.

All I'm saying is I want very light conversation traces. Nothing heavy like Google Wave is necessary.

When two sides are clearly

When two sides are clearly having a discussion, and then a third party appears to jump in, it gets confusing, especially with anonymous comments.

Yes, this is exactly what I had in mind. These random interjections are the anti-thesis of the articulate, cogent arguments found here on LtU. Whether or not this is due to threading, as I implied, or something else, as you suggested earlier, is up for debate.

Diving into thread trees depth-first, or skimming threads breadth-first is up to you. Seems well suited to my learning style at least.

Backtracking is also fairly easy; not so on Ward's wiki, where you have to mentally track to whom you assigned which randomly interjected comments.

Clarification

I see you probably misinterpreted what I said.

Not being able to delineate who is talking can often result in subtle reading difficulties. I often ask myself, "Did this guy just contradict his earlier position? Is he coherent?" That's why knowing who is talking is important.

Tracking Changes/Popularity

The recent changes page for ward's wiki - shows a lot of small deltas. The format doesn't lend itself to mapping that to popularity. I'm skeptical whether most people using the web actually understand that the news flow of a "wiki" shows up in some page buried somewhere on the site that tracks changes. One PLT related wiki that I look at periodically is compiled by Eelco Visser here.

Patterns discussion re-loaded

Sometimes, there is no HOWTO manual for how to use the Internet the best...

it helps to hear somebody say "use this section of the Internet this way", giving you a combination of etiquette, style and substance advice.

...If you are interested in patterns discussion, Ward's Wiki is not the ideal place to get the information (IMHO). Instead, see Hillside Patterns Library. It is way more organized. Clickin on the Catalog link at the bottom left of the page will direct you to a list of pattern languages. Some of these pattern languages are hosted at c2, but in a different section of the site than the WikiWikiWeb, i.e. The Portland Pattern Repository. This part of c2 is not quite the same collaborative model and is much more coherent.

Follow up

Luke Gorrie wrote:

Is WardsWiki the best hack ever? The impact per line of code is unbelievable.

Simplicity at its best. It is interesting what a challenge like "simplest online database possible" can lead to, maybe a nice exercise is to think about the "simplest XXX possible" and see what results.

naasking wrote:

I've always found that wiki hard to follow. LtU discussion threads have a more rigorous, linear progression, which I find very easy to follow and results in good retention. Particularly if you're new to this stuff, the progression from what at first seems like a sensible idea, to why it runs into problems leading into the final solution is instructive.

So if a wiki had a better threading mechanism, could it practically replace a forum? I was thinking what if people can reply to specific paragraphs inline, but you would know who was replying and when through a ID/timestamp. Perhaps color could also be used, with the ability to ellide comments of a post so you could read it as originally written. I'll definitely check out ether pad mentioned by Z-Bo.

No one really mentioned the archival power of Wiki: the ability to refactor topics to be more general or specific as needed, and continue discussions over long periods of time. Is this just not useful, I mean, are people ok with repeating similar kinds of topics over and over again just because we can't refactor existing ones?

Types and online communities

Perhaps it's all because the layout of LtU is statically typed, but wikis are latently typed.

Is that irony or prophecy?

Etherpad

nagios & ubuntu cdrom drive failure debugging

Etherpad was acquired by Google about a week and a half ago. When first acquired, Google blocked all creation of new etherpads and told users they had until March to save their etherpads. It now seems they've reversed that decision.

Sometimes what we'll do at work when somebody is remoting, we'll set-up gotomeeting, a phone call, and etherpad. This is how we do code reviews remotely. Etherpad is honestly the ultimate groupware "glue tool".