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.
Re: Why are companies now requiring techical writer candidates to be SMEs?
Subject:Re: Why are companies now requiring techical writer candidates to be SMEs? From:Martha J Davidson <editrix -at- nemasys -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 22 Apr 2003 16:17:20 -0700
I think "ignorance" has been misused in this discussion. I agree that being
ignorant of tools and technologies has never served me as a technical writer.
On the other hand, having a new user's perspective as I learn a new
technology has been immensely valuable. When I apply for jobs documenting a
technology that I am only peripherally familiar with, this is what I sell.
The more I pay attention to my own experience learning the software I
document, the more I can clarify the parts I found confusing when I was
starting out.
I choose to only document software, with a preference for software
development tools. What I bring is familiarity with a number of aspects of
this area of software, though I've seldom been hired to document a tool or
development process that's exactly like one I've documented before.
Instead, I start with an understanding of what software developers do and
experience having done it myself many years ago.
Over the years, I've worked with many different tech writers. The ones who
were the most successful also had a foundation in software development,
even if they had never written code themselves. I find that I can often
tell from reading a chapter written by a writer I don't know well whether
that writer was familiar with the subject or not. I try to make my
comprehension of the underlying technology show through everything I write
and every question I ask of a developer. Otherwise, I'll just be parroting
words I hear, with no real idea if I'm making sense or not.
To summarize, I agree that ignorance is never a good thing for a tech
writer to sell in a job search, but the perspective of a neophyte (who
strives to become a power user) can be a valuable skill, expecially for
writers who retain that perspective even after becoming power users.
martha
--
Martha Jane {Kolman | Davidson}
Dances With Words
editrix -at- nemasys -dot- com
"Everything should be made as simple as possible, but no simpler."
--Albert Einstein
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Last chance to order RoboHelp X3 and receive a $100 mail-in rebate,
PLUS free RoboScreenCapture and WebHelp Merge Module. Offer expires
4/30/03! Order here: http://www.ehelp.com/techwr-l
Help celebrate TECHWR-L's 10th Anniversary starting this month!
Check out the contests at http://www.raycomm.com/techwhirl/special/contests/
Happy birthday to you, happy birthday to you, happy birthday TECHWR-L....
---
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.