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.
FWD: Re: re Pros and Cons of including writer's name
Subject:FWD: Re: re Pros and Cons of including writer's name From:"Eric J. Ray" <ejray -at- RAYCOMM -dot- COM> Date:Fri, 29 May 1998 07:08:30 -0600
Name withheld upon request. Please reply on list.
*************************************************
Hear, hear! We have some pretty poor writers at this company, and my work
gets tossed in with theirs in our User's Guide. If my name was on it, and
the person reading it didn't know which parts were mine....
I get enough pride out of my work without having my name attached to the
work. If I want my name on it, I'll write my own book (like our esteemed
listowner and spouse have).
On Thu, 28 May 1998, Lisa Higgins wrote:
> I've been waiting for someone else to bring this up, but maybe I'm
> really the only one.
>
> I wouldn't want my name associated with about 70 to 80% of the stuff
> I've written.
>
> I'm not complaining, really. It's my job to write and produce what my
> company or my client wants. And they almost always want some pretty
> stupid things. Maybe the design is cumbersome. Maybe the manual has a
> "Conventions Used in this Guide" section (Good grief!!!), maybe some
> illiterate CEO made me include something about software that makes
> "extensive use of the function use native to modern computing" or is
> "a cornucopia of functional richness," or maybe there's just a bunch
> of extra stuff in there that shouldn't be there.
>
> I'm not deeply ashamed of too many things I've done, but I'm still
> not interested in taking complete credit or blame for someone else's
> style guide, template, illustration, or document requirements.