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: A brief intro and a few newbie questions From:"Jeff Hanvey" <jewahe -at- comcast -dot- net> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 28 Oct 2003 11:03:00 -0500
I'm going out on a limb, and steeling myself for controversy, but here goes.
I'm not long out of the newbie phase myself - The job I currently have is
only my second "real" techwriting job, and I've been at it for just over a
year. Prior to that, my previous job as a writer lasted a little over a
year, but was rather limited in scope. I've identified myself as a
techwriter for four years or longer, which is why I don't consider myself a
newbie. I'm still learning a lot about the field...
I advocate that you don't spend your time *just* studying English grammar
and writing...spend some time reviewing the job ads in your targeted
geographical location to determine what skills are requested most often.
Learn those skills to make sure your competative and marketable in that
area. This is regardless of what type of skills they are - technological,
tools, or deliverables.
I've spent a lot of time in the job market, and I found that hiring types
aren't flexible. They don't listen to "oh, I know the *theory* of help
files." They want to know you've created a help file. With the software
they've invested in. Same with paper manuals, or whatever.
Take the time to use these products and create the types of files - even if
you do it on your own...
Being a sys admin, I'm sure there are *plenty* of things to document around
the job. Create these docs in mulitple formats, both paper and electronic,
and consider multiple audiences. (for example: what would a person majoring
in systems administration need to know? What would the run-of-the-mill
college student need to know?). If you have the inclination, use each
product to create the various formats. For example, create a FrameMaker
doc, and use Acrobat and WebWorks to convert the docs to PDF and HTML/Help.
Recreate the doc in RoboHelp and do the same. Add those pieces to your
portfolio.
If you have the funds, check with your college bookstore - there may be
academic versions of all the software available at a reduced cost, just so
you can learn them.
----- Original Message -----
From: <newsletters -at- benbailey -dot- net>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Sent: Monday, October 27, 2003 3:53 PM
Subject: A brief intro and a few newbie questions
>
> I've read a lot about RoboHelp and FrameMaker, but do not have access to
> these programs. Do companies expect entry-level writers to be familiar
> with these applications?
RoboHelp for FrameMaker is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to online Help, intranet, and Web.
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! Call 800-718-4407 for
competitive pricing or download a trial at: http://www.ehelp.com/techwr-l4
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
