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:Tech Writer's Test From:David Blyth <dblyth -at- QUALCOMM -dot- COM> Date:Mon, 18 Dec 1995 13:36:02 -0800
>I hope your test questions are tongue-in-cheek.
Some were, some weren't.
The bottom line is that Tech Writing is about communication.
Thus, a student Technical Writer needs to learn how to observe
carefully, think clearly and for themselves, and not to make
assumptions about what they document.
There are some tears in this, a lot of laughter, and a lot
of hard work. But don't take everything I say so seriously! ;)
>Your test is not a test; it's a damn obstacle course with a
>bunch of hidden traps
So is Real Life. I still certainly intend to _write_ the test.
Still, you don't need to _ give_ the test to every student on every
level. For example,
o On the JC level, you could pull problems off the test and
work through them in front of the class.
o In an Upper Division class, you could include one or two
problems from the test on a real test (warn the class
o In a Graduate Program, warn the class about Gotchas then
actually give the test!
o In Real Life, we all face these questions and worse. And
in Real Life, we can laugh!
One person didn't see any smilies so wondered if I had any