Learning quickly

Subject: Learning quickly
From: John Posada <jposada01 -at- yahoo -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 28 Nov 2001 08:19:59 -0800 (PST)

I'd like to discuss a comment that someone recently posted. Mind you,
I agree with the comment.

"You need to be able to learn new, often difficult things, very
quickly"

My question...how is this done. Does it mean that the writer must
simply be brilliant and extremely smart (as is my case :-) ) or does
it mean that someone must know a technique or skill on how to do
this?

Or does it mean that before you put Word-One on paper, that you must
spend days and days pondering every spect of the subject?

Putting aside those who are brilliant, what is that technique?

I'll assume that this technique not only covers the ability to learn
the subject being written about, but also when you need to learn
something quickly to write WITH.

I'll throw out the my observation.

Learning something quickly is not so much an issue of learning
EVERYTHING about the subject, but more a prioritization skill in
knowing what to learn first. Personaly, I prefer to start getting
"something" on paper immediately, even if it is basic stuff that will
be built on (or trashed and replaced). It makes me feel better that I
feel productive and if makes the boss feel better if something is
created.

Take learning a software tool, such as a word processor. In my case,
I don't learn everything about that tool, but only what I need to use
at that moment. I'd start with how to launch a blank screen. Enter a
few words, now learn how to save the new document. There...I know 50%
of what I'll need to know to start producing a deliverable.

Extend this technique to learning about what I'm writing about. We'll
assume this is for software, though the approach logic can extend to
anything.

First, learn how to start it and how to close it. Once you know that,
the rest is details, since you cannot do ANYTHING if you cannot start
it. Now, pick it apart piece by piece. I usually do this in the order
that functions appear in the menus. If this was a browser, the first
thing I'd start with it File -> New. then File-> Open. Simply work
through the menu from beginning to end.

Funny thing about this sequence...usualy, the creation of the Help
Application comes after the paper documentation and being that it is
at the end of the menue sequence, by the time I'm at the end and hit
Help, I'm ready to write the Help.

Does any of this make sense?

=====
John Posada, Senior Technical Writer
mailto:john -at- tdandw -dot- com, 732-259-2874

__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of
your book. What are you waiting for? http://www.iuniverse.com/media/techwr

Have you looked at the new content on TECHWR-L lately?
See http://www.raycomm.com/techwhirl/ and check it out.

---
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.


Follow-Ups:

References:
RE: tech writing: From: Malone, Jay Ms., RCI - Vienna

Previous by Author: RE: Tech writing list nothing more than a way to get e-mail addre sses to spammers?
Next by Author: Re: Ethics and Job-Hunting
Previous by Thread: RE: tech writing
Next by Thread: Re: Learning quickly


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


Sponsored Ads