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.
At 10:31 AM 03/14/2000 -0800, John Posada wrote:
>...the first time someone took my documents "in the
>back" to review them, they were copied and they at-
>tempted to not have me know they did it (it occurred
>to three documents, each document was stapled at a
>different angle and they attempted to match the
>angle and have the staple perforations match)...
There is another issue at stake here. Those of us who design and/or
document inhouse computer systems have impressive, professional-looking
manuals/user guides/brochures -- which unscrupulous individuals could use
to have their own applications written.
The main difference between a developer and a programmer is that the
programmer is given a task, and writes code to accomplish that task --
while the developer first ascertains the need, then determines the
requirements, then assigns and/or performs the tasks, etc. If you hand a
good programmer a well-written user guide,
he can probably use it to create a system which would otherwise have taken
years to put together. That would prove really upsetting (to say the
least) to a company that worked very hard to create an inhouse system they
considered unique.
