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:Writing Test? From:"Mark L. Levinson" <nosnivel -at- netvision -dot- net -dot- il> To:TechWr-L <TECHWR-L -at- LISTS -dot- RAYCOMM -dot- COM> Date:Sat, 20 Nov 1999 18:37:39 +0200
Tony Markatos says:
The problem with writing tests is that they are based on the
assumption that the major task of a Technical Writer is the
drafting of text.
Not exactly. We test the drafting of text because it's testable.
Other factors may be just as important but aren't as easily tested.
If the writer can't write, though, then other competencies are kind
of moot.
Marc Santacroce wondered whether we test contractors the
way we test FTE writers. Personally I don't, and I rather
believe that I'm wrong. I examine samples from a contractor,
and I figure that the contract itself should give me sufficient
opportunity to escape in plenty of time if the work turns out
to be lousy. How likely is it that I'll get lousy work from a
successful contractor anyway? So far in my experience the answer
is "very likely" and the schedule seldom allows for a restart
from scratch, so I'm thinking of changing my ways.
--------------------------------------------
Mark L. Levinson - nosnivel -at- netvision -dot- net -dot- il
--------------------------------------------
