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: "Technical Writing: How to Break Into this Lucrative
Subject:Re: "Technical Writing: How to Break Into this Lucrative From:Kaylin Tristano <kaylintristano -at- quadax -dot- com> To:"techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 1 Apr 2015 12:20:49 +0000
How else are we to find out what REALLY goes in the documentation? I thought making up crazy stuff and giving it to the engineer to correct was SOP?
I'll give the author of the article credit, what she's describing really is most likely an entry-level technical writer position. You don't know much, you write simple things, you learn more over time and work your way up to the "crazy ass" stuff.
Kaylin Tristano | Quadax Technical Communication Specialist
Date: Tue, 31 Mar 2015 16:10:30 -0400
From: John G <john -at- garisons -dot- com>
To: Chris Morton <salt -dot- morton -at- gmail -dot- com>
Cc: "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
Subject: Re: "Technical Writing: How to Break Into this Lucrative
<CAFJnaP5ES5RSAsRmd=YYMzV=pOrSo02nwYAThxJn+3VFKOpodQ -at- mail -dot- gmail -dot- com>
Content-Type: text/plain; charset=UTF-8
That's what I keep doing - the only review comments I get are to crazy ass
stuff that I make up!
Adobe TCS 5: Get the Best of both worlds: modern publishing and best in class XML \ DITA authoring | http://adobe.ly/scpwfT