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:Responses to my "Grammar & Rhetoric..." posting From:JohnBrin <johnbrin -at- AOL -dot- COM> Date:Tue, 7 Jun 1994 00:32:03 -0400
In the last 24 hours, 16 of you responded to or posted something
related by my message about "grammar and rhetoric." All but one
showed interest in discussions about the topics I suggested.
That one told me that I was doing it wrong-that I shouldn't suggest
topics but present them. That was my intention, if others showed
interest. The interest appears to be there, so I'll contribute some
of my ideas about using innovation and technology to do new things
new ways (as opposed to using innovation and technology to do old
things new ways). I'd appreciate others contributing to this
Most of you who said something related to the topics I suggested
commented about combining training and documentation. I believe I can
make a case for doing just that. Separate development of training and
documentation can result in significant duplication of effort. Keep
in mind that the real objective of both training and documentation is
to promote user performance. If document developers and training
developers collaborate, duplication can be minimized, the elements of
training and documentation can complement each other, and the whole
effort can benefit from the fact that two (or more) heads are better
And that brings to mind sill another new-things-new-ways topic:
Collaborative development by cross functional teams, using team
members from marketing, engineering, support services (including
training and documentation), and customers.