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.
The second-most-important item on the task list is "Maintain records
and files of work and revisions," which at least for me was automated
years ago.
It reads like a job that's mostly editing other people's work with a
lot of computerizable clerical activities. There were jobs like that
during the dot-com boom but I think most of those people have been
shaken out of the profession.
On Fri, Jan 2, 2015 at 8:55 AM, Robert Lauriston <robert -at- lauriston -dot- com> wrote:
> Here's the entry for technical writers from O*NET, which provided the
> bulk of the data for the study's algorithm:
>
>http://www.onetonline.org/link/summary/27-3042.00
>
> The Tasks section includes mostly things I never do ("arrange for
> typing"?) and is missing the core tasks I spend most of my time on.
>
> Garbage in, garbage out.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1pJ4zPa
