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.
Re: Is this a typical technical writing environment?
Subject:Re: Is this a typical technical writing environment? From:jposada -at- isogon -dot- com To:techwr-l -at- lists -dot- raycomm -dot- com Date:Fri, 20 Feb 2004 11:12:10 -0700
Lucy...if you write great content, have a PhD in CompSci and know tools
inside and out, you only know 3 of the 4 necessary sklills to be a writer.
The forth one is how to position yourself so you find out about changes
without you chasing them or them chasing you.
Find out how developers know amoung themselves what's going on, what is
changed, what's changing, and what's scheduled to be changed. Maybe they
have daily status meetings and you want to be included. Maybe they have
internal discussion groups and you want the address. Maybe they hang out
in a particular section of the building and you want to prowl the floor
striking up a conversation whenever you can.
What you don't want to do is whine to them "Why didn't anyone TELL me?"
That's not their job to tell YOU. It's their job to make it known, you
just have to be a recipient of that knowledge.
