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.
One reasons that developers/programmers don't do such a hot job of
documenting their own software is that they're too familiar with it. They
can't "back off" and look at it through the eyes of the poor user who's just
taking it out of the box and doesn't know diddly about how it works.
Well, I'm finding writers can end up in the same boat. I have to write some
very general introductory material for some software I've been documenting
at a detailed level, and I'm having trouble looking at it from the outside.
Anyone having any thoughts, point of view, etc., on how to handle this?
Sponsored by SOLUTIONS, Conferences and Seminars for Communicators
Publications Management Clinic, TECH*COMM 2001 Conference, and more http://www.SolutionsEvents.com or 800-448-4230
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.