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.
I don't know what anyone else's intentions in this thread were,
but I didn't think any of the messages on this subject accused you
of being unethical. I just thought we were discussing possible answers
to the question: What do we do when we encounter kludgy stuff in
the software we're documenting?
The bottom line for all of us seems to be "make it easy for the user" --
and thankfully, doing so is also in the company's best interest!
Faith Weber
weber -at- easi -dot- enet -dot- dec -dot- com
