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.
In my limited experience, I have found myself very much in the loop, acting
as a "consultant" on template creation, layout, and training. I have been
asked for suggestions about how the docs should be constructed and output.
Chris
> I should note that, from my experience and from
> talking with others who do some remote work, the
> nature of the work and the writer's involvement is
> very different than being on-site. You are quite
> removed, and are measured and held accountable ONLY
> for the work agreed upon. Very seldom do you have
> input for change, and best practice advice is only
> well received 50% of the time. Basically, as a remote,
> you're being hired to perform a task and get it done.
> You're most-often an accessory and not a key
> contributor.
>
> FWIW,
>
>
> =====
> Goober Writer
> (because life is too short to be inept)
