Being a Web Developer I have but one natural enemy in the wild, and that is documentation. Developers have written tons of software to transform documentation from a foe to a friend. I've use several of this applicattion, NDoc being a great application I use the most for this task. It that takes the comments in your code and create and MSDN style .Chm file to document the methods and properties of your application. However this kind of documentation is only useful to other Developers. Otherwise I write documentation up in Word.

The problem with that is I don't like Word. Don't get me wrong Microsoft makes a fine product, but it doesn't work like I do. Creating documents in Word is a very laborious process to me that required dedicated time, time that I usually don't have to invest. This is were a Wiki comes in. What is a Wiki. Well This is how Wikipedia defines a Wiki"

Here a wiki (IPA: [ˈwiː.kiː] <wee-kee> or [ˈwɪ.kiː] <wick-ey>^[1]) is a type of website that allows users to easily add, remove, or otherwise edit all content, very quickly and easily, sometimes without the need for registration.

So basically it's a website that you can edit, or add content to any time you think about it. Now this works for me. I always have a web browser open, so I always have the tool I need to do my documentation open. To me a website of this methods is a much more active type of documentation, when you read it, and see something is missing you just add to it, edit it delete whatever. A Word document is very static to me, because the barriers, you have to open a heavy application, make sure you have acess to the document, make sure it's not locked by any other users. To me Word documents are a centered around one person. Where a Wiki is much more group based and that is one of the big draws for me.

We are a small department at work with a lot of knowledge. However what happens if one us aren't there. Well usually a phone call is placed, because of being small department with a lot to do, one persons ends up having the specific knowledge needed at the time. Well a Wiki offers a great solution to that problem. I'll give you an example, today a mission critical application experience some dramatic slowness,  while there was a persons that could have recycled the application they didn’t know how. Someone else had to be called and do it remotely. While being about to do the task remotely is great, wouldn’t it of been much faster for the person that was already in and awake to do the task. I’d have to say yes. So I took 5 minutes took some screenshots and wrote and tutorial on how to recycle the application and now anyone in the team can look it up and take care of the task.

So now we are doing are documentation in a Wiki, it is fast, easy and dare I say fun.