Wiki Refresher

I have been using wikis[^plural-form] for quite a while now. So long in fact that I had forgotten exactly how much better they are than the alternatives. I started my new job a few weeks ago and started evangelizing the wiki that had recently been installed. Last week the developer who sits next to me wrote up a bunch of notes about the current iteration in the wiki. After just an hour or so of using it she was totally convinced. It reminded me of how I felt the first time I used a wiki.

The low barrier of entry makes continuous documentation[^after-the-fact-docs] tenable. Prior to the wiki we were using Sharepoint, which as far as I can tell, goes out of it’s way to make documenting things as difficult as possible. Already there are things documented in the wiki that would never have been documented in Sharepoint because Sharepoint is just too painful. If your group does not already have a wiki you should set one up[^twiki]. Today. You will be glad you did.

1 thought on “Wiki Refresher

  1. So I’ve been screwing around with a one page application called TiddlyWiki. In the course of messing with it, some of the people in the community have looked at creating a server integration so that multiple people can use tw, and have it store stuff on the server. This is creating an interesting tool in that we may be able to have a documentation system that caches all of the wiki entries in an html file sitting on your system (so you have acccess to it offline) but will also update itself to the latest server wiki entries the next time you are on a network. The experiences of working for Integware have really helped with the code I am writing for this, as essentially it appears possible to turn tiddlywiki into the front end of an entire document control system.

    Oh, and adding new syntax is a snap, as well as adding plugins.


Comments are closed.