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.
In article <199410031532 -dot- IAA17829 -at- infinity -dot- c2 -dot- org>,
Richard Mateosian <srm -at- c2 -dot- org> wrote:
>Let me expand on points one and two by saying that I believe that there are
>more significant paths through the software and more relevant interactions
>of features than you could possibly include in a 1000-page manual in 9-point
>type. Therefore, it seems to me, that (1) you can't learn (meaning
>understand completely) the software (meaning all of its features and
>interactions) from a manual, and (2) it's only going to get worse as
>programs get bigger and more complex. ...RM
I don't think that on-line help, per se, can do any better than a paper
index combined with See Also references in the text. The true advantage
of on-line "help" can best be seen with the new Expert/Wizard features;
many of these newfangled tutorials actually work with data you supply,
so you can learn while accomplishing something useful.
--
--- Aahz (@netcom.com)
Hugs and backrubs -- I break Rule 6
Androgynous kinky vanilla queer het
The best way to get information on Usenet is not to ask a question,
but to post the wrong information.
