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: Writing vs. Testing From:Anthony Markatos <tonymar -at- HOTMAIL -dot- COM> Date:Sat, 22 May 1999 13:00:56 PDT
Rebecca Merck wrote (in response to a question asking if TWs need to be
software testers):
And let's be honest -- if I wanted to be a tester, I'd have applied for a
job in QA, right? The skill sets are different, the professional
experiences are different, and the best of tech writers without a QA
background is the lowliest of testers (as Fred experienced).
Tony Markatos responds:
I disagree. The primary task of a (software) technical writer is to gain a
clear, concise, and systematic understanding of the essential tasks that the
end user performs with the application. This is exactly same as the primary
task of a end user software tester. The skill sets (and experiences had in
obtaining such skill set) are the same. A technical writer with this skill
set will be the highest level software QA person.
Tony Markatos
(tonymar -at- hotmail -dot- com)
_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com
