Re: Hi all

[John Cook <john -dot- cook -at- gmail -dot- com>]

On 1/19/06, Pragya Gupta <pragya -dot- gupta -at- smartchiponline -dot- com> wrote:
>
> Hi All,

Hi, Pragya!

> I am Pragya, a new joiner of this group. I would like to thank you people
> for creating and maintaining technical writing group, which provides immense
> help to a newbie like me.

This group and other speciality groups, like the HATT (Help Authors
Tools and Techniques, http://groups.yahoo.com/group/HATT/), have
helped me make the leap from a self-taught writer wannabe to techncial
writing as a professional career.  The knowledge that exists in these
groups and the various mentors who have selflessly and patiently
answered my questions have all been vital in my goal to become an
effective writer.  Lists like this and these mentors have been
invaluable to me as I learned the ropes (so to speak) and gained
experience as a fully-fledged technical communicator.  I've written a
rambling essay (that started out as a post here for the TECHWR-L) on
my writing blog here:
http://phywriter.com/how-i-became-a-tech-writer-and-other-stories/

> Can you please tell me what will be expected from me as a technical writer
> in a product based company, considering the fact that I am the first and
> only technical writer of this company? I have a bit of experience of
> working in an e-learning company as a technical content author, where I used
> to author technology books. So I don't know what to expect here...apart from
> help document.
>
> Thanks in advance....
>
> Regards,
> Pragya

They will expect miracles, however, the best you can provide is clear
documentation customized for your company's end-users.  Know your
audience and remember the priorities of tech writing (as written by
Andrew Plato on this list in 2001):

1. Content (accuracy)
2. Presentation (structure)
3. Grammar (language)

Everybody's got a favorite platform (when I was getting started, I
learned Adobe FrameMaker in three days going through their Classroom
in a Book), but the tools you use are less important than the output
you provide--clear, accurate documentation of how to use a product or
accomplish tasks.

You are embarking on a grand journey, and I wish you great success!

Kind regards.
--
John Cook
Technical Writer / Help Author
john dot cook at gmail dot com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l

Doc-To-Help includes a one-click RoboHelp project converter. It's that easy.  Watch the demo at http://www.componentone.com/TECHWRL/DocToHelp2005

---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -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%40infoinfocus.com

To subscribe, send a blank email to techwr-l-join -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.