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 work in the conditions you are about to face. I enjoy the environment,
however, I have shifted my job definition a bit. I approach the work first
as a software developer, second as a writer. This perspective is important,
since you will be now associating with developers on the team more than with
the fellow writers. You will identify yourself more with the software team
rather than with the writing team.
Working on a development team can be hard, because the tech writer is
generally considered the least technically proficient member of the team,
and programmers generally judge all people by their technical abilities. I
would recommend brushing up on your computer skills far beyond that demanded
by your job. This will facilitate communications and good professional
relationships with the programmers, which is vital for successful
documentation (also dramatically boosts the resume).
And remember, programmer HATE to do documentation, and they should be
extremely grateful that you are a part of their team. If not, then remind them.
Gotta run, good luck,
St. Louis, MO
dandam -at- 1stnet -dot- net
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-