RE: Technical writer survey: What should we really call ourselves?

Subject: RE: Technical writer survey: What should we really call ourselves?
From: "Dan Goldstein" <DGoldstein -at- riverainmedical -dot- com>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Thu, 13 Aug 2009 08:30:49 -0400

Just in time for the thread -- here's a reality check from a local writers' e-mail list this morning:

"The technical writer will be responsible for creation of print and online documentation, user guides, how to pages, cheat sheets and other training materials for variety of tools/applications/products implemented. It will include creation of simple websites using Google Sites or plain HTML/CSS. Technical writer must have experience in creating graphics that will be used in training materials, such as screen shots, diagrams, visualizations."

As Gene suggests, it might be unwise in this case to use "Technical Communicator" as the title on your résumé. It would suggest an inability to follow simple instructions.

P.S.: When they want a technical writer to "have experience in creating graphics that will be used in training materials," they're even happier to get one who knows how to lead the training.

> -----Original Message-----
> From: Lippincott, Richard
> Sent: Tuesday, August 11, 2009 1:32 PM
> To: techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: RE: Technical writer survey: What should we really
> call ourselves?
>
> We can call ourselves whatever we want, but the -real-
> question that is being asked here is "What do we want other
> people to call us?"
>
> We may not be able to control that.
>
> I suspect "Technical writer" is probably the most common term.
>

This message contains confidential information intended only for the use of the addressee(s). If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing, copying, electronic storing or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this message by mistake, please notify us, by replying to the sender, and delete the original message immediately thereafter. Thank you.

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

Free Software Documentation Project Web Cast: Covers developing Table of
Contents, Context IDs, and Index, as well as Doc-To-Help
2009 tips, tricks, and best practices.
http://www.doctohelp.com/SuperPages/Webcasts/

Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/ for more resources and info.

Please move off-topic discussions to the Chat list, at:
http://lists.techwr-l.com/mailman/listinfo/techwr-l-chat


References:
RE: Technical writer survey: What should we really call ourselves?: From: Lippincott, Richard

Previous by Author: RE: Technical writer survey: What should we really call ourselves?
Next by Author: RE: Have We Entered a Post-Literate Technological Age?
Previous by Thread: Re: Technical writer survey: What should we really call ourselves?
Next by Thread: RE: Technical writer survey: What should we really call ourselves?


What this post helpful? Share it with friends and colleagues:


Sponsored Ads