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.
Once again, I think the issue is who you're writing for and what
you're writing. My BA's in English (Milton's a dead poet) and my MA's in
"Humanities," an ad-hoc program that enabled me to put together writing
and communication (as in Communication, the social science).
My science training is limited to high school and my own reading
and experience (work). I worked with an Industrial Engineering consulting
outfit for years as an analyst. My computer training is a mish-mash of
COBOL, JCL, and early "this is a computer" stuff (including Wang word
processors!!). My software skills are a
mish-mash of DOS, Mac, and Windows programs.
I've written about dynamometer controllers, water treatment
, manufacturing equipment, and gun trajectories. Where I've been able to
be the most successful (the document does what it was supposed to do) is
when I've enabled the client to tell me what the document is supposed to
and when I've had a chance to talk to at least a couple of users.
From there, I can construct the contents and develop an approach.
I disclaim responsibility for the technical accuracy. Instead, I rely
on the technical expertise of my SME to ensure that, if you plug A to
B, it won't blow up. My job is to tell you how to plug A to B.
BTW, I agree that curiosity and interest in technical stuff is
what makes this fun!
Mary Durlak Erie Documentation Inc.
East Aurora, New York (near Buffalo)
durl -at- buffnet -dot- net