No subject

> For a professional writer, grammar is an important tool of=20
> the trade. If I am interviewing writers and a candidate=20
> cannot tell me what an imperative sentence is, what passive=20
> voice is, or why diectic pronouns require clear anticedents,=20
> they don't get hired. Period. No mater how nice they seem or=20
> how good their portfolio looks.=20

These are some odd requirements.  Give me an example where knowing "why
diectic pronouns require clear anticedents" is necessary for technical
writing?  Show me a passage written by someone that violated this rule
and
the violation was a direct result of not knowing this rule of grammar.
I do
not know the rule and will probably be able to correct the passage
because
good writing is about good writing and not about knowing the rules that
define it.  The rules were written after good writing was recognized and
learning the rules will not automatically make a good writer, yet a good
writer will follow the rules and not necessarily know them.

Your claim that you would not hire a person with a good portfolio that
could
not answer grammar questions leads me to believe that you value the
rules of
form over the function of documentation.  Can you answer the question
"What
is the function of technical communication?"

I use grammar and I certainly was not trying to say that it is a tool
that I
do not use.  But I did not think that my discussion of semantics
required a
scholastic discussion of grammar.  I am not familiar with all the terms
of
grammar and it is not required that I should be familiar with these
terms to
discuss semantics or to maintain my professional writing career.  A
person
that can define terms and not write according to the rules of those
terms is
not a better candidate than a person that can write according to proper
grammar rules and not define them.

Personally, I would not want to work with a manager that was only
interested
in candidates that can define grammatical terms.  I would feel as though
I
was working with someone whose background is in English Literature or
Journalism.  Personality types from those areas are good people, but not
really very technology-oriented, from my experience.  I have also found
that
editing work from such types is a bit of chore because the documentation
tends to be wordy and vague.  Although such people can make excellent
marcom
writers.

Lauren=20

> -----Original Message-----
> From: techwr-l-bounces+lt34=3Dcsus.edu at lists.techwr-l.com=20
> [mailto:techwr-l-bounces+lt34=3Dcsus.edu at lists.techwr-l.com] On=20
> Behalf Of Susan W. Gallagher
> Sent: Monday, February 05, 2007 11:37 AM
> To: Techwr-l
> Subject: RE: The 'user' in User Manual
>=20
> To my way of thinking, a professional who is unfamiliar with=20
> the tools of their trade is not much of a professional. A=20
> chef can tell a ramekin from a french knife; an auto mechanic=20
> is intimately familiar with both torque wrenches and crescent=20
> wrenches; a doctor can tell a stethescope from a=20
> sphignomanometer. If they did not know these things, we would=20
> certainly wonder about them; their credibility would be in jeopardy.
>=20
> For a professional writer, grammar is an important tool of=20
> the trade. If I am interviewing writers and a candidate=20
> cannot tell me what an imperative sentence is, what passive=20
> voice is, or why diectic pronouns require clear anticedents,=20
> they don't get hired. Period. No mater how nice they seem or=20
> how good their portfolio looks.=20
>=20
> Then too, it's a technical writer's job to learn things, and=20
> most revel in doing so. In my more than 20 years of technical=20
> writing, I have never encountered a *talented* technical=20
> writer who wasn't eagerly accepting of new knowledge about=20
> the tools of the trade or the technology on which they're working.=20
>=20
> IMO, a writer who does not know grammar and has no desire to=20
> learn is a writer without credibility.
>=20
> My two cents - your mileage may vary.
> -Sue Gallagher
>=20
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>=20
> Create HTML or Microsoft Word content and convert to Help=20
> file formats or printed documentation. Features include=20
> single source authoring, team authoring, Web-based=20
> technology, and PDF output. http://www.DocToHelp.com/TechwrlList
>=20
> Now shipping: Help & Manual 4 with RoboHelp(r) import!=20
> New editor, full Unicode support. Create help files,=20
> web-based help and PDF in up to 106 languages with Help &=20
> Manual: http://www.helpandmanual.com
>=20
> ---
> You are currently subscribed to TECHWR-L as lt34 at csus.edu.
>=20
> To unsubscribe send a blank email to
> techwr-l-unsubscribe at lists.techwr-l.com
> or visit=20
> http://lists.techwr-l.com/mailman/options/techwr-l/lt34%40csus.edu
>=20
>=20
> To subscribe, send a blank email to techwr-l-join at lists.techwr-l.com
>=20
> Send administrative questions to admin at techwr-l.com. Visit
> http://www.techwr-l.com/techwhirl/ for more resources and info.

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

Create HTML or Microsoft Word content and convert to Help file formats
or=20
printed documentation. Features include single source authoring, team
authoring,
Web-based technology, and PDF output.
http://www.DocToHelp.com/TechwrlList

Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com

---
You are currently subscribed to TECHWR-L as ccondo at c-cor.com.

To unsubscribe send a blank email to=20
techwr-l-unsubscribe at lists.techwr-l.com
or visit
http://lists.techwr-l.com/mailman/options/techwr-l/ccondo%40c-cor.com


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

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