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.
Subject:RE: Quality of source material from Development From:Salan Sinclair <salansinclair -at- shaw -dot- ca> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 12 Dec 2001 16:01:55 -0800
Your situation is exactly what my friend is trying to get started --
developers provide and maintain a spreadsheet that lists the command syntax,
description, and other technical reference material. The tech writers can
refer to this spreadsheet when writing and maintaining customer documents.
Other posts indicate this situation is rare.
But thanks for letting me know it actually does occur elsewhere.
Salan
Sandy Harris wrote:
A division I've seen work well in several projects is that programmers
write Unix man pages (or the equivalent on other systems), terse highly
technical reference material. I then write other things -- documentation
for end users, tutorial material for developers using the API, design
rationale docs to help sell the product, procedural info for system
administrators, ... -- whatever else is needed.
One very handy side effect of this is that I can use the version control
system to track changes to the man pages. This means I learn of most
software changes that affect my docs, without having to rely on
developers remembering to email me about them.
This requires that the programmers be literate and that their management
include documenting the code as part of their requirements. Neither of
those is always the case, but in my experience both often are.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of
your book. What are you waiting for? http://www.iuniverse.com/media/techwr
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.