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.
I didn't think of this before I answered. I said one project at a time, but
I didn't define a project as a single manual. I maintain several manuals.
When it's time to update, the same changes usually need to be made in more
than one manual. Thus, I define updating the "manuals" as one project. As
opposed to another project which would be producing a new manual for a new
product.
I like/need variety, but prefer to define a project, start it, and finish it
without interrupting it for another project. I can concetrate and remember
the details better that way. And I hate having to put away all the source
materials (notes, scribbles from engineers, examples, printed pages, etc.)
for a project, knowing I am not done and will have to drag them all out
again. I hate when my desk gets such a mess that I can't find things. At
that point, I have to stop and organize.
Janet
Janet Valade
Technical Writer
Systech Corporation, San Diego, CA mailto:janetv -at- systech -dot- com
> -----Original Message-----
> From: Rock, Megan [SMTP:Megan -dot- Rock -at- fanucrobotics -dot- com]
> Sent: Monday, February 19, 2001 6:53 AM
> To: TECHWR-L
> Subject: RE: New TECHWR-L Poll Question
>
> I'd be curious how other people defined the term "project" when they
> answered the poll question.
>
> I've never worked on just one project at a time, but my definition of
> 'project' in the context of my work is "any task that is different in
> scope
> or detail from another task." I might be working on one setup & ops
> manual,
> but I usually have several unique features that I am documenting at the
> same
> time, working with different developers and SMEs for each feature.
> Perhaps
> some of you would say that since my end product will be one manual, I'm
> actually working on one 'project' with multiple tasks.
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Develop HTML-Based Help with Macromedia Dreamweaver 4 ($100 STC Discount)
**WEST COAST LOCATIONS** San Jose (Mar 1-2), San Francisco (Apr 16-17) http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.
Sponsored by ForeFront, Inc., maker of ForeHelp Help authoring tools
for print, WinHelp, HTML Help, JavaHelp, and cross-platform InterHelp
See www.forehelp.com for more information and free evaluation downloads
---
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.