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.
> *Ideally,* the tester would be someone who has
> the same
> level of technical literacy as your expected
> user but little or
> no knowledge of the particular product under
But they do have, because well before testing
documents, the test engineer has been testing the
features of the product. OTOH, a peer will do
fine because, *ideally* we do the things that we
document: install, destroy log files, crash, and
recover. Troubleshooting info is typically served
up - all issues and solutions we cannot fathom;
and release notes; and API/SDK documents.
If we don't do things that we document, and only
take input and clean it up for language, then it
is editing. Some call it proofreading -
On an unrelated note, was it Baudulaire who would
go into depression and seclusion for months
together after completing a book (feeling
terrible about his output). Happens to the best
of them French writers, what?
Thanks and regards,
Sankara S Rajanala
+358 50 428 0702
Tina: I am an experienced technical writer.
You are an intern and a rodent, respectively.
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l