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.
Re: Post on the misconceptions about technical writing
Subject:Re: Post on the misconceptions about technical writing From:Shawn <shawn -at- cohodata -dot- com> To:John G <john -at- garisons -dot- com> Date:Tue, 25 Nov 2014 15:49:52 -0800
As I began reading this eleven year old list, I didn't understand the
disparaging comments. I mean, one of the first tasks I took on was to build
a rudimentary style guide. I work in a start-up with a new doc
department... so yes, some standards need to be established. In my
experience, all the larger, well established corporations actually care
about and enforce strict adherence to the style guide(s).
But I very quickly realized that this list is purely sarcastic... ha ha...
this person condensed down most of the stereotypical ideas that a young
whipper-snapper thinks are important in technical writing. In *my* reality,
not a single point is remotely close to true. I found "2. Remain
Writer-focused" particularly funny. In my position, if I didn't understand
the technology, I would not have the ability to competently document our
products. In fact, in my overall experience content has always been far
more important than style.
On Mon, Nov 24, 2014 at 12:02 PM, John G <john -at- garisons -dot- com> wrote: