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.
Subject:Re: More on Validating documentation From:kcronin -at- daleen -dot- com To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Mon, 25 Mar 2002 12:53:03 -0700
Bruce and Dick argued thus:
Bruce:
>>But, on the whole, developers are a closed community of introverts. By
>>comparison, writers are extroverts.
Dick:
>Uh, I don't think so. Some of us (maybe some of the most successful of
>us, maybe the ones you know and like) are extraverts. I suspect that the
>majority of tech writers fall on the introvert side of the median.
I'm with Dick on this, and I think it identifies one of the roots of this
age-old problem.
<BEGIN SWEEPING GENERALIZATION>
Many writers are drawn to the written word as a "safer" medium of
expression than actual spoken exchanges between actual live humans. And
the same could be said of many developers, whose mastery of code exceeds
their social skills. Put these two introverted species together and the
probability of a communications impasse increases exponentially.
</END SWEEPING GENERALIZATION>
But to climb back on my soapbox, an even bigger contributor to the problem
is when the entire corporate culture supports the notion of developers
being supreme beings, who need not stoop to accommodate mere wordsmiths.
Companies like that are a drag, believe me!
Incidentally, I'm an extrovert (this is no doubt a surprise to some of
you), and for the most part have found this trait to be a MAJOR asset in
trying to communicate with developers. Through humor, schmoozing, and
strategically-asked questions that demonstrate I've done my homework, I've
been able to defrost all of the developers I've interviewed. The biggest
challenge is getting them to actually meet with me. One I get them pinned
down for the interview, I'm able to get what I want.
Then, while the tranquilizer dart is wearing off, I tag the developer's
ear, so I can set him free back into the wilderness when the interview is
over. (Oops - had a Andy Richter fantasy - sorry!)
-Keith Cronin
________________________
I'm probably part of the problem. Hell, I'm probably part of MOST
problems.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PC Magazine gives RoboHelp Office 2002 five stars - a perfect score!
"The ultimate developer's tool for designing help systems. A product
no professional help designer should be without." Check out RoboHelp at http://www.ehelp.com/techwr
---
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.
