TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Part Time QA? From:Sara Stewart <sara -at- sara-stewart -dot- com> Date:Tue, 22 May 2007 14:06:10 -0400
Interestingly, this is an issue that also came up for me recently. As a
routine part of documentation, I have been submitting bug reports and
instances of typos or inconsistencies in the interface. My current
employers decided they liked this service so much, they've not only
adopted my method of error reporting as the company standard, but also
are moving me into formal testing. (I get to learn their testing
harness later this week.)
I personally think doing testing is a great fit with technical writing,
and I love working closely with developers, so I'm quite happy about it.
I have a similar background to PTW, I think, though. If you're not
sure about whether you'd like it or not, you might want to do some
research on QA processes (if you have inside information, so much the
better), and see how you feel about it. Of course, you probably already
did that. :)
Just my CDN$0.02 (now at a 30-year high in informational value!). Take
care, and good luck!
Sara Stewart
Pro TechWriter wrote:
> Personally, I really like the opportunity to do QA on a project. My skillset
> can really be valuable, because of my usabilty experience (garnered doing QA
> and user interface design), a tech writer's attention to detail :-) and the
> ability to communicate what the defects are, why they are defects, and
> suggestions for fixes if the defect is in the UI, error messages, or other
> user-oriented areas.
>
> Geoff is correct that working more closely with the developers is a benefit.
> They came to appreciate my ability to keep track of all the changes, and my
> input as a "user advocate."
>
> A final benefit of the experience is that I have three career tracks when
> jobs are scarce: QA tester, requirements analyst, and technical writer.
>
> Good luck with your decision.
> PT
>
>
--
Sara Stewart Communications
Technical Writing, Editing,
and Specialty Research Services
www.sara-stewart.com
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-