Access to software versions: a rant

[Cardimon, Craig]

<< So she asked me: "But why do you need access to the software?" >>

I encountered a certain level of hesitancy when I asked for access to
different things. Saying I was the new technical writer wasn't really
enough from a diplomatic standpoint. 

I learned to say I was the technical writer and I needed access so I
could update the user guide. I would accomplish this by running the
software and documenting how it functioned and making new screen
captures along the way.

Maybe the developers thought I was hunting for bugs and would point a
finger when something didn't work. No one wants to have their mistakes
pointed out in an accusatory fashion. I made sure I said I was not
interested in blaming anyone and would not. And I haven't.

When I find something I believe is a bug or an inconsistency, I document
it. Then I take it to my manager and demonstrate what I have found. He
decides if it is worth pointing out to the higher-ups and basically
explains the "why" to me. Not everything is worth fixing, from a
cost-effective point of view. So far my instincts have been pretty good.

Craig