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.
"Strict technical writing" is when you get wacked across the knuckles with a ruler for every error that appears in anything you publish.
-----Original Message-----
From: techwr-l-bounces+lporrello=illumina -dot- com -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+lporrello=illumina -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of Dan Goldstein
Sent: Friday, September 07, 2012 10:42 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: RE: Rhetorical question about Information Design
Let's see: Organization, presentation, digging out information, judging information's usefulness, and creating information from scratch. That could easily be a senior technical writer's job description; I do all that. (Yes, my job title is "Quality Assurance Manager," but that's another thread.)
I have no clue what "strict" technical writing is.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.
Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.
