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: Ethical Question - RESPONSE - From:Bill Burns <BillDB -at- ILE -dot- COM> Date:Wed, 6 Jan 1999 10:01:13 -0700
This is the second post I've seen responding to Andrew's comments, and I
just have to butt in (my obssessive-compulsiveness rearing it's ugly head)
and comment.
Look, foax--we as professionals keep touting the idea that the documentation
is part of the product, not just a peripheral piece. A-and we keep claiming
that we should be as much a part of the product development team as the
programmers and engineers. When they develop a crappy product and we simply
document it without pointing out the problems, then we are doing are part in
the whole scheme of crappy product development. We can't have it both ways.
Granted, I've been in on my share of product horror stories. (Hey, I'm a
vendor. It's part of the territory.) Part of doing your job well is learning
how to deal with folks who DON'T do theirs well.
'K, so maybe this was only worth a ha'penny.
Bill Burns
ILE Communications Group
billdb -at- ile -dot- com
Call me fishmeal.
