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.
>> Now I have a new opportunity! My current employer has asked me to help
>> move the company in a new direction. He'd like me to join the
>> development team in the beginning of the next project and write *all*
>> the documentation, including that which the programmers would otherwise
>> have written.
I've had that chance before. Unfortunately, how it goes depends on your
programmers. Mine were quite willing to forget I existed and not invite me
to design meeting, keep me informed of changes, etc.
Work hard to stay inside the loop, including yelling loudly early if they
push you aside. On the other hand, if you are a full team member, work hard
to get the interface designed well and then the documentation becomes easy.
