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.
As discouraging as it may be to read published
comments extolling the virtues of NOT reading the
documentation in order to learn a system, there is
merit in those comments.
As I'm sure other experienced writers have had happen
to them, I've been asked in the past what could be
done to reduce the amount of documentation needed by a
system or product. My answer always is that they
would have to design the system or product for users.
Even then, I don't think you will eliminate the need
for documentation, but how much you need can be
lessened by making the parts that users use intuitive,
self-descriptive, and easy to use.
Lest that sound pessimistic, I have yet to have anyone
who asked me the question take my answer seriously.
So I'm not expecting to be out of work anytime soon
(unless I hit the lottery or learn of a rich distant
relative who has died and left me independently
wealthy. Applicants for such a position will be
favorably received.)
