RE: The Problem with STC

[Alan -dot- Miller -at- prometric -dot- com]

Michael West has taken exception with Andrew Plato's views with regard to
the relative importance of technical knowledge and writing skills. The
answer is very simple (to my mind): Mr. Plato is correct Mr. West is
incorrect. There, that was easy. :-{)

Before we, as *technical* communicators, can clearly explain a complex
technical concept, we must thoroughly understand that concept. This
requires research, curiosity, and a thoroughgoing understanding of "first
principles," the fundamental mathematics and science behind the technology.
This is "depth of knowledge," something I see lacking in most of my
dealings with fellow STC members. I say this not as a criticism of the STC
or my fellow members, it is simply a fact. Most of us are involved in the
documentation and communication of computer-related technologies and tend
to forget that that is not all there is. (I can quote from pop culture,
too. :-{) ) Computers and computer software are pretty simple stuff,
compared to, say, the design and theory of operation of a nuclear power
plant. Try explaining the thermal performance of a nuclear reactor (even to
a lay person) without classical and nuclear physics, thermodynamics,
calculus, material science, chemistry, and fluid dynamics. Clearly,
computer hardware and software are *not* a nuclear power plant. The
technical skills for the computer are far easier to acquire. But you still
gotta have 'em.

I don't know about this "accepted wisdom" or the "mountains of empirical
evidence," having not seen the studies. Be glad to read them if Mr. West
will point me to the ones of his choice. In the meantime, I can argue from
anecdotal evidence. I have had better results training engineers to be good
writers than training writers to be good engineers. That is not to say that
it cannot be done, it's too time-consuming to be practical (outside the
computer industry, and even here it is border-line. I've won a few and lost
a few.). Which is exactly why Westinghouse Steam Turbine Division, General
Electric Steam Turbines, Stone & Webster, Bectel, Brown and Root, Burns and
Rowe, Babcock & Wilcox, Asea Brown Bavaria, Deutsche Babcock Anlagen,
Daniels International, and every other major engineering firm I've had
contact with use engineers to prepare their product documentation and send
out engineers to educate their users in the use of their products. (Of
course, these guys know their audience: other engineers.) I know, I've
worked with these folks, and in some cases, helped train their engineers.
Workable and successful.

A weak technical background means, to me, the writer lacks the knowledge to
differentiate between a correct statement and an incorrect statement, or
between complete information and incomplete information. Then the writer is
forced to over simplify complex concepts or use inaccurate or incorrect
analogies by way of explanation. As a result, the reader misunderstands or
fails to understand the concept at all. If the reader didn't understand,
the technically weak writer cannot try another approach, another
explanation, or another analogy. How can (s)he reframe an idea that (s)he
does not fully understand him(her)self?

This is a hot-button topic for many of us. I would be very interested to
see how the opinions are split according to the advocate's background
(i.e., which position do those with technical backgrounds and those with
non-technical backgrounds espouse). Has this been studied, or polled?
(Hint, hint. Nudge, nudge. Ms Ray.)

Your ob't savant,
Al Miller
Chief Documentation Curmudgeon
Prometric(r), Inc.


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Develop HTML-based Help with Macromedia Dreamweaver! (STC Discount.)
**NEW DATE/LOCATION!** January 16-17, 2001, New York, NY.
http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.

Take XML and Tech Writing courses online!  Our instructor-led courses
(4-6 hrs/wk) give you "hands on" experience at your convenience. STC members
get 20% off!  http://www.online-learning.com/index.html.
---
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.