awakeThere is a nightmarish side to my lovely programmer's world. It seems that I have to write documentation for my creations. There is an interesting twist that drives me to do this. The average database application has core users that HAVE to use the software. They will learn the ways of the program via one-on-one instruction, their own handwritten notes, and perseverance. It is part of their job. I can write a very minimal amount of documentation for these people. The rest of the people who could use the application, but aren't forced to, require more documentation and instruction. In theory, this documentation has to be pretty thorough. Yuck. BUT, this is work that must be done if my creations are going to spread further.
I could write this documentation. Hmmm... I could also just move onto another application or add new 'neat' features to an existing one (which is what I'm doing today). In the end I will write the documentation. My sense of work integrity says that I need to provide documentation for that time when I am not here. It is the problem of other people if they don't take advantage of it. Sides, better docs will allow my creations to further infest the company, I mean to say, more people will find the utility in my hard work. (smile)
