For the past few days, I'm creating how-tos on modifying some codes on a website. My problem is that, its one of the least enjoyable tasks that I have been doing and im getting impatient on it. Documentation is not my turf, my thesis groupmates would attest to that.. I'd rather code and design than doing that. Anyway, the task is, I've got to list the steps on how I went around my coding, complete with screenshots and all, since it will be another person who will be tinkering around with the development asp scripts.

Months before, when just started working with the company, I was enjoying a newbie-like life. The project manager, which is the Director of Technology, which is the No.2 guy in the company, which is literally my boss, when giving me a new task, would give me a file complete with instructions and how-tos in getting around the task done, yes, that's right, project documentation. (presumably, it was the project manager who was doing the instructions and putting it to ms word), now its my turn to do that, in case there will be someone who will be editing the real mccoy. so, after countless trips to the kitchen to get water, im back here at my desk and feeling enlightened. ive realized that maybe this task is:
  • somewhat a 'sign' that im gaining the trust of the project manager, since he's delegated some of his tasks to me.
  • another addition to my resume entry, i can add this to my resume, instead of the usual, "Developed and Designed blah blah website", id be typing, "Created procedure documentation and standard code writing with blah blah website."
  • a confirmation that POST, which i read somewhere, is very important. POST stands for Project according to Organizational STandards. Literally translated it means that you have to do 70% documentation and 30% coding – so, I really got a taste of the amount of documentation that i will be doing when in production.
I'm beginning to love creating documentations..

No comments: