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 agree here. Content may freeze for just once day in my case. Then it's
back at what the developers have done so far and what are the client
requirements.
Most of the time, your manager wants to impress his manager and you are the
one re-writing the doc about 20 times for one release.
My advice is speak to the developers as much as you can and keep yourself
informed of what is staying in the doc and what is going. Don't be suprised
if there are features added last minute. I'm saying this because most of the
time, the manager will have no time to give you details. Keep calm and write
up an outline before you start. Try and do the most you can to make the
dealine and any change that is not a "major" change (code or software), tell
your boss it will go in the next release. and if he says no, then ask him to
help you write. That way you save time and all you do is type.
Hope this helps,
