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.
-----Original Message-----
From: Mark Baker [SMTP:mbaker -at- omnimark -dot- com]
> "Best documentation" should be saved for documentation that solves a harder
> problem.
I don't agree with this at all. "Best documentation" is whatever communicates
effectively to its audience. I don't think it's reserved for only "harder"
problems.
The lego instructions, for example, tackle the complexity of the process of
building (vs. assembling) something which is essentially free-form, and
communicates it to a target audience aged 5-12.
For the record, I see the difference between assembling and building as this:
assembling is a pre-determined pattern, every one you make will be exactly the
same. Building is how to put the components together to build whatever you
want, with each one potentially being the same or each one being completely
unique.
How would you document a "process" where every end product is different?
--
Lisamarie Babik
lmbabik -at- winspc -dot- com
Documentation Specialist
