As part of my work, I must document everything.  Being a code monkey it is sometimes hard to change gears between coding and documenting.  When I do get around to documentation there are odd things that happen that make me realize I have been coding too much.  As a result, I've compiled the list below.

This is a list of things that happen to code monkeys when they try and write documentation:

- your sentences end with semi-colons

- you try and delete lines of text with shift-delete

- rather than ctrl+s to save your document you hit ctlr+shit+b to build

- you try and comment-out various parts of your documentation

- when someone asks you for a technical spec you send them the code

- your document headings start with "public void"

This is my very first blog.  I have never blogged before... but every now and again I think I should.  The reason for this is quite simple - sometimes when I have a problem (relating to development) I find many different potential solutions.  Only after searching thousands of posts do I finally find something that works... the real solution is typically a combination of those few hidden gems inside forum posts.  When this happens I think to myself: If i had a blog, I could share this information so the next poor sucker doesn't have to go through the same tedious hell that I went through.  So, after many years of thinking, I finally decided to act with what you see here. 

-Gord