This too is technical communication

[John Posada]

> skills and their inherently superior insight into user needs, are 
> *already* equipped to add value in these areas that those who
> work in them now cannot, and that therefore their roles should 
> be expanded and any company that does not do so is foolishly 
> ignoring a valuable resource.  

About two weeks ago, I was caught up and had a day to "waste", so I
asked one of the QA guys here if he would mind if I just got a feel
of what he did with the application I was documenting.

Now, I always thought I was sharp and prided myself on how I found
bugs, but HOLY CRAP! I was blown away by what he did on a day to day
basis. The depth to which he knew the application, the operating
system environment (Linux), the ability to request server changes to
test various configurations, and just seeing stuff on screens as they
flew by me faster than a speeding bullet made me walk away with my
tail between my legs. I was humbled.

The next time anyone who is trained as a technical writer believes
that he should be the QA go-to guy should be ashamed of
themselves...you don't know what they really do.

John Posada
Senior Technical Writer

"They say everyone needs goals. Mine is to live forever.
So far, so good."