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: Can someone shed some light on the following terms ...
Teach a person to fish ...
Mostly at the beginning of a software project there is a list of things the
software will eventually do. This list reads a lot like *both* the project
plan *and* the outline of the user manual. This is just one of many very
good reasons that the technical writer be part of the project from the
beginning. Another is that the writer gets to know the developers/engineers
and can ask them questions such as these. This should be a major advantage
of having in-house writers vs contracting out (but of course there can be
smart contracting). Directing these questions to this list indicates a
level of detachment from the development team that will likely prove not
productive.
IPCC 01, the IEEE International Professional Communication Conference,
October 24-27, 2001 at historic La Fonda in Santa Fe, New Mexico, USA.
CALL FOR PAPERS OPEN UNTIL MARCH 15. http://ieeepcs.org/2001/
---
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.
