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: What would I call this? From:jarnopol <jarnopol -at- interaccess -dot- com> To:Melissa Girardot <books -at- paulding-net -dot- com>, TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 31 May 00 16:14:58 -0500
Melissa Girardot books -at- paulding-net -dot- com write:
<snip>> =====
>Some time ago, I found myself writing training manuals concerning the
>mainframe programs I used in my clerical jobs, right down to "press
>this key to get this result".
>I'd like to be able to include these manuals on my resume, but I
>honestly don't know what to call them, or whether they would even be
>applicable to any tech writing jobs I might apply for.
<snip>
How about calling them what they are? "End-User manuals for xxxx (name of
function) on an xxxx (name of machine) mainframe"
They sound like instruction manuals, possibly quasi-instructionally designed.
Just decide on a name and make sure you have a copy in your portfolio.
