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.
"David Neeley" <dbneeley -at- oddpost -dot- com> wrote in message news:223882 -at- techwr-l -dot- -dot- -dot-
> While I agree fully with all you have said on the subject, I would add
that a frequent problem is that "everyone thinks he's a writer"--what we do
seems so much less exacting than coding (for example) that it appears simple
in contrast.
>
> I would agree that it *is* simpler than programming for the most
part...but not so much simpler as many would assume. Of course, the degree
of difficulty always depends upon the level of talent and underlying
technical knowledge.
I'm not sure I really agree, in large part because programming has become
much easier and in some part because getting information where you want it,
how you want it, isn't really different from programming in many situations.
A lot of programming code is now automated. Windows, buttons, and other GUI
widgets are pre-coded, and characteristics of those items are set in a GUI
interface. SQL queries are created in a graphical environment. I could go
on.
But no program can write a cohesive, grammically and contextually correct
sentence that explains how to use a programmer's creations.
Whether it be English or C++, it's just languages. Put that way, Tech
writers have the toughest job because English is by far the largest and most
complex language with the least rigid rules of syntax, grammar, and meaning.
>
> As for "defining ourselves"--while as I said I agree this is important, in
many cases we must ask the question "If we don't do it, who will?" In other
words, many tasks we are called upon to do seem to require far less talent
and experience than we (should) bring to a given situation. For instance,
many tech writers chafe at being asked to take notes of developers'
meetings. However, what they may not be crediting is the ability of the one
who keeps the minutes to do much to define the scope of the project. In
fact, I have found it is often a very good practice when being in *any*
meeting on the job to send a memo to the meeting participants afterward
detailing the information presented and the decisions reached in that
meeting. Often enough, this is a "CYA" step that can save a great deal of
misunderstanding and disgruntlement later. (By the way--I've often seen
people "disgruntled," but darn if I've ever seen anyone who might admit to
having been "gruntled!").
>
I cna't speak for others, but taking notes beyond what I need for my own
job, such as comprehensive notes for the entire team, makes it far, far more
difficult to actually participate in development meetings.
But then I infer that you don't think that tech writers *are* developers,
and if that's what you meant, I'd disagree. We're just a developer of a
different breed.
At companies that seem most successful and with least dysfunctional teams,
I've seen what works most often is that product managers themselves take
those comprehensive notes, because they are herding the process and letting
the developers do the actual hashing out, then distributing the meeting
summary to the team afterward.
--
--
Chuck Martin
User Assistance & Experience Engineer
twriter "at" sonic "dot" net www.writeforyou.com
"I see in your eyes the same fear that would take the heart of me. The day
may come when the courage of Men fail, when we forsake our friends and break
all bonds of fellowship. But it is not this day! This day, we fight!"
- Aragorn
"All you have to decide is what to do with the time that is given you."
- Gandalf
RoboHelp for FrameMaker is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to online Help, intranet, and Web.
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! Call 800-718-4407 for
competitive pricing or download a trial at: http://www.ehelp.com/techwr-l4
---
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.
