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.
Tracy Boyington wrote:
>
> Sandy Harris wrote:
>
> > Anne Nonymous wrote quite a good post, but titled it:
> >
> > "Positive feedback from supervisors"
> >
> > This triggers a pet peeve of mine. ...
>
> (Eric, I promise, this *is* related to tech writing).
My previous post was not intended as a personal attack on anonymous.
My apologies if it sounded that way. I was trying to raise the questions
which Tracy asks more clearly below.
> ... When jargon leaves its boundaries, don't we eventually have to accept
> it? At what point do we, as professional communicators, stop saying "you can't
> use the term that way because that's not what it originally meant," and *start*
> saying "since most of the world thinks X means Y, it's time to recognize that X
> means Y"?
If the term has a clearly defined technical sense, e.g. "positive or
negative feedback"
from cybernetics or "positive or negative reinforcement" from
behaviourist psychology,
I don't think it is /ever/ correct to use it in a way that ignores or
contradicts that
sense, e.g. using "negative reinforcement" to mean "punishment".
> This interests me because I'm in education and have some
> responsibility to educate as well as inform. Is anyone else occasionally caught
> between the "correct" way and the effective way to communicate?
The word "hacker" is a nice example of this. Does it mean a skilled
programmer (the
original sense) or a system-breaker?