Re: Good/bad docs

Subject: Re: Good/bad docs
From: Max Wyss <prodok -at- PRODOK -dot- CH>
Date: Sat, 8 Aug 1998 00:01:27 +0200

Sella,

this has been a "philosophy" for some time. It is true to some extent (you
get at the product and kind of know what to do, opposed to first learn
weird key combinations to do anything at all). But even then, you may need
documentation.

Most of these companies do not make non-computer products. For machinery,
there are pretty strict requirements, and there that "philosophy" will fail
for sure. For example, in order to use the CE sign, certain documentation
must be provided in at least the leading language of the country the
product should be marketed. OK, it is mainly safety related stuff, but
according to the Machine Regulation, documentation is part of the product,
and without documentation, the product is not complete, and may not be sold.

Another Zweiräppler.


Max Wyss
PRODOK Engineering AG
Technical documentation and translations, Electronic Publishing
CH-8906 Bonstetten, Switzerland

Fax: +41 1 700 20 37
e-mail: mailto:prodok -at- prodok -dot- ch or 100012 -dot- 44 -at- compuserve -dot- com


Bridging the Knowledge Gap ...

... with Acrobat Forms ... now for belt drive designers at

http://www.prodok.ch/prodok/riemen.html




_____________





>And then there's the companies and/or developers who insist that their
>product is so intuitive it doesn't need documentation. In fact, including
>documentation is an admission that their product needs help.
>
>Sella Rush
>mailto:sellar -at- apptechsys -dot- com
>Applied Technical Systems (ATS)
>Bremerton, Washington
>Developers of the CCM Database


From ??? -at- ??? Sun Jan 00 00:00:00 0000


Previous by Author: Re: art as role in tech writing
Next by Author: Re: Is there a market for a dual-purpose font
Previous by Thread: Re: Good/bad docs
Next by Thread: Re: Good/bad docs


What this post helpful? Share it with friends and colleagues:


Sponsored Ads