RE: Taking Credit

[Beth Agnew <Beth -dot- Agnew -at- senecac -dot- on -dot- ca>]

Perhaps I am fortunate never to have experienced those negative side
effects. For every instance I am aware of where writers had their names in
the documentation, the outcomes were only positive. Putting one's name on
something should be a stamp of quality. It's also appropriate to get the
credit you deserve for the work you have done. Developers names often are,
and should be, displayed in software. Even though the manual may be the
product of a team, the names of those involved humanizes it. Ego is not part
of it; rather a commitment to quality and standing up for what you've
produced.

Any bad behavior that others exhibit as a result of seeing your name in the
manual is not a reason to stop doing it.

-----Original Message-----
From: bounce-techwr-l-118812 -at- lists -dot- techwr-l -dot- com
[mailto:bounce-techwr-l-118812 -at- lists -dot- techwr-l -dot- com]On Behalf Of Bill
Swallow
Sent: Saturday, March 26, 2005 10:37 AM
To: TECHWR-L
Cc: TECHWR-L
Subject: Re: Taking Credit

My company took the names out several years ago.<snip>

It's certainly nice to see your name in print in association with a
product you helped complete, but be aware that it can have unpleasant
side effects.




^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo:
http://www.webworks.com/techwr-l

---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.