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.
--- Berk/Devlin <armadill -at- earthlink -dot- net> wrote:
> Respectfully, I need to disagree a little at least.
> There are some areas
> of technical writing in which being a quick study
> and asking intelligent
> questions does not cut it.
Oh, I quite agree, Berk! The thing is, there are so
many kinds of tech writing that needs to be done, that
you can't have a cookie-cutter writer who can do them
I wasn't seeing my comments about my approach to tw as
being "better" in any way, merely stating that this is
*my* approach. It gets me the jobs I want to do.
Your skill is in programming; mine is in being a
ferret. This is not to say that you are not good at
asking questions, nor that I can't read a program if
pushed (I can). It's more a matter of interests,
personal style, and inclination - and you can't argue
with Gus about which is better; there are times when
each of us is the right writer for a given project.