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.
Can someone give me insight into the process of
creating user's guides, installation manuals,
or such product information?
I am an inexperienced tech writer-to-be, and
I am about to interview with a company as a tech
writer with the responsibilities of creating
the above mentioned product documentation. I
have good written skills, but being new to
the field of tech writing, I don't know how tech
writers generally manage the process from start
to finish. I imagine that sometimes tech writers
will have to start the documentation from scratch
and sometimes work with revising and updating
such product literature. But maybe some of you
who are more familiar with this process could
fill in the picture more for me, especially
if starting from scratch and how you go about
this task.
I am just a newbie who is looking for more information
so I can learn more about this field and develop
my tech writing skills. This will definitely
help me be a more prepared interviewing candidate also.
By the way, I have looked through the archives,
and haven't seen anything about this *basic* question
( I know).
This would really help a lot. Thanks.
Feel free to respond to me personally,
sirinya16 -at- hotmail -dot- com
Sirinya Laiteerapong
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
