Re: Technical Writing and Software Testing

[kafkascampi <kafkascampi -at- gmail -dot- com>]

At my company, the entire engineering staff (including me, the one writer)
does round 2 testing before a release of our SaaS application. I'm also
part of the design process. And compliance documents, training videos,
managing the translation, writing the help, writing the manuals, writing
the wiki, uh....

Maybe I should hire someone.

But cheers, Craig. Glad you are getting some recognition.

Chris

On Wed, Feb 8, 2012 at 9:11 AM, Cardimon, Craig <ccardimon -at- m-s-g -dot- com> wrote:

> Agreed.
>
> -----Original Message-----
> From: Dana Worley (MVP/JB) [mailto:dana -at- campbellsci -dot- com]
> Sent: mercredi 8 février 2012 12:11
> To: Cardimon, Craig; 'techwr-l -at- lists -dot- techwr-l -dot- com'
> Subject: Re: Technical Writing and Software Testing
>
> Yes, but if you are "paying attention" and actually using the product
> while writing documentation, you will find bugs and usability issues. If
> you shrug these off as someone else's job to worry about, then you are
> doing your company a disservice and missing an opportunity to add value in
> your role as a technical writer.
>
> You may not have access rights to enter issues into the database, but you
> certainly have the responsibility to bring issues to someone's attention.
>
> Dana
>
> On 2/8/2012 9:59 AM, Cardimon, Craig wrote:
> > While "anyone" can write documentation, not everyone is allowed to
> really put the software through its paces, testing for and submitting bugs.
> >
> >
>
>
>
>
> --
> *************************************
> Campbell Scientific, Inc.
> Product Manager, Software Products
> *************************************
> Microsoft Help MVP 2002-2012
> *************************************
> Jester's Baubles Fused Glass Designs
> http://www.jestersbaubles.com
> http://jestersbaubles.blogspot.com
>
> Information contained in this e-mail transmission is privileged and
> confidential. If you are not the intended recipient of this email, do not
> read, distribute or reproduce this transmission (including any
> attachments). If you have received this e-mail in error, please immediately
> notify the sender by telephone or email reply.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as kafkascampi -at- gmail -dot- com -dot- 
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
> http://www.techwhirl.com/email-discussion-groups/ for more resources and
> info.
>
> Looking for articles on Technical Communications?  Head over to our online
> magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions?  Search our public
> email archives @ http://techwr-l.com/archives
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email archives @ http://techwr-l.com/archives