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.
>
>At the companies for which I have worked, Easter Eggs of any kind have
>been frowned upon. Now, I get a kick of them, like anyone would, and
>nothing would give me bigger thrills than putting the developer's home
>phone numbers and cell phone numbers in some secret, Easter-Egg location
>in the online help (okay, lots of things would give me bigger thrills
>;?), but here's the reasons I've been given in the past for company
>action against Easter Eggs:
My goodness Sean, we don't do anything as high tech as that! May I
suggest a little thought along the lines of acrostics and anagrams.
As I mentioned a few weeks ago. I use the ragged right edge of user or
machine name lists as an acrostic. Since I get to sign my work now, I
no longer use it.
>I'm sure there are other reasons. Anyway, one of the things I would face
>in putting names on a software doc would be anyone who was interviewed,
>sent an e-mail about the book, caught a typo, or whatever, would want to
>be put on as a contributing author/editor.
The idea is to be able to take credit internally. The signature should
be invisible to anyone who is not in on the secret.
Another benefit is that you can use it to verify a claim of
authorship.
For example: A suspicious old b*st*rd like me, having been presented
with the world's greatest manual as part of your portfolio, might be
inclined to view with suspicion your claim to be its author. If you
can point out the signature it would help to substantiate your
statement.(I am, having been dazzled by your verbal pyrotechnics,
already persuaded that you have written such a manual.) ;->
>Indeed, top spots would go to
>people far higher up the food chain than any technical writer, and, in
>turn, those folks would try harder to micromanage their project. Project
>titles, like "Editor in Chief," and "Senior Copyeditor" would be handed
>out as honorary titles and those in the trenches would feel more
>slighted than had their names not appeared at all.
Three little words Sean, "need-to-know." So far as I'm concerned, no
one needs to know but you and those you *choose* to share it with.
>
>And, before you say it ain't so, Joe, buy me a beer at a conference and
>I'll explain it to yah.
I'll buy you a beer for the sheer joy of spending the time pounding on
the table and talking loudly.
-Doc
David W Lettvin
VerText
South Hamilton, MA
978-468-1105
ADMIRATION, n. Our polite recognition of another's resemblance to
ourselves.
-Ambrose Bierce
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Save $600: Create great-looking Help files and software demos with
RoboHelp Deluxe. Get RoboHelp and RoboDemo - our new demo software - for one
low price. OR Save $100 on RoboHelp Office in June with our mail-in rebate.
Go to http://www.ehelp.com/techwr-l
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
