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:Re: Good Manuals - Why Rare. From:Chris Hamilton <cah_91 -at- yahoo -dot- com> To:techwr-l -at- lists -dot- raycomm -dot- com Date:Thu, 16 Mar 2000 05:49:59 -0800 (PST)
>> Scottie Lover said:
....If you hand a good programmer a well-written user
guide [written by a competitor company],he can
probably use it to create a system which would
otherwise have taken years to put together.
Do you really think so? I'm not being fecetious, but I
am struggling with this.
Depending on the product, my assumption is that you
shouldn't innundate the reader with details about the
internals, except on a need-to-know basis. I need to
test that theory, it seems. From a business
standpoint, this seems like something you _wouldn't_
want to do. I guess my question is, _should_ we write
to enough detail to let someone reverse engineer the
product? My initial thought is that we shouldn't, but
I'm willing to be trained by people with more wisdom
and experience than I have.
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com