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.
Subject:Re: So now we are content engineers? From:Tony Chung <tonyc -at- tonychung -dot- ca> To:Lauren <lauren -at- writeco -dot- net> Date:Thu, 7 Nov 2013 11:54:30 -0800
On Thu, Nov 7, 2013 at 10:04 AM, Lauren <lauren -at- writeco -dot- net> wrote:
> On 11/7/2013 9:53 AM, Tony Chung wrote:
>
>> It's not about content or format, but rather the systems and means to get
>> the right information into the right hands at the right time. Sounds like
>> engineering to me.
>>
>
> Designing systems according to specifications is engineering. Designing
> means is process analysis. Reducing system engineering and process analyses
> to a writing is technical writing.
>
If the specifications are about the content flow, and not the content
details, then it falls under your engineering definition above.
I know lots of "Technical Writers" who don't write content.
-T
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.