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.
For those of you who work with software developers, how do you
find out what software changes affect the documentation?
Do you have to bug the developers? Do you read through Design
Documents? Do you just play with the software and document what
you find?
Please let me know your thoughts by e-mailing Paul -dot- Carman -at- harris -dot- com -dot-
I'm moving out of my tech writer position, and I'm working on
developing procedures so that the new person won't be totally lost
when it comes to document updates. I've always spoken to the
developers to find out changes, and I find that this method
stops being effective when the developers leave the company!
Thanks for your input!
-MacGyver
-----------------------------------------------------------------------------
= Paul MacGyver Carman * =
= Harris Corporate HQ * Choose to chance the rapids, =
= (407) 724-3205 * and dare to dance the tide... =
= (407) 724-3627 (fax) * =
= Paul -dot- Carman -at- harris -dot- com * - Garth Brooks =
-----------------------------------------------------------------------------
