Monday, October 18, 2010
I've taken on a role in my latest project that I lovingly refer to as "Documentation Whore." I won't go into all the geeky reasons I'm not thrilled with being the Documentation Whore. The documentation has to be done, and I'm pretty good at doing what needs to be done and explaining to the compliance trolls when something isn't necessary. (This is because I still have that scrap of optimism which imagines a world where the documentation actually helps someone. Most of us are well beyond that point, and see the documentation as meaningless busywork. Coincidentally, this is probably why I'm the Documentation Whore.)
The problem is that people insist on inventing new documents. The trolls only want a specific set of documents explaining what insanity you've wrought over the course of your project. But there's a host of other people who seriously just invent documents and then ask you to produce them, and a lot of what we end up doing is regurgitating the same content into a variety of different templates. Seriously, sometimes it's just easier to produce something that looks like what people are expecting than it is to educate them about why what they are expecting is insane or asinine (or both--why limit ourselves).
And so another day passes where our entire project team is convinced that Scott Adams has installed surveillance equipment in our workplace.