<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to Break into Technical Writing</title>
	<atom:link href="http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/</link>
	<description>Technical Communication Blog / Technical Writing Blog</description>
	<lastBuildDate>Mon, 22 Mar 2010 08:03:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ragnar</title>
		<link>http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/comment-page-1/#comment-138897</link>
		<dc:creator>ragnar</dc:creator>
		<pubDate>Sun, 29 Mar 2009 03:59:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/#comment-138897</guid>
		<description>Thanks for sharing!</description>
		<content:encoded><![CDATA[<p>Thanks for sharing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/comment-page-1/#comment-132118</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Mon, 16 Jun 2008 21:11:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/#comment-132118</guid>
		<description>Kris, I think I answered your question with this post: &lt;a href=&quot;http://www.idratherbewriting.com/2008/06/15/how-can-i-become-a-successful-technical-writer/&quot; rel=&quot;nofollow&quot;&gt;How can I become a successful technical writer&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Kris, I think I answered your question with this post: <a href="http://www.idratherbewriting.com/2008/06/15/how-can-i-become-a-successful-technical-writer/" rel="nofollow">How can I become a successful technical writer</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kris</title>
		<link>http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/comment-page-1/#comment-132117</link>
		<dc:creator>Kris</dc:creator>
		<pubDate>Mon, 16 Jun 2008 21:06:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/#comment-132117</guid>
		<description>I have an English degree plus a Master&#039;s Degree in Lib Science.  I&#039;ve writen a lot of stuff in college, but don&#039;t know what happened to it since.  What can I do to show the employers that I have what it takes to be a Tech Writer?</description>
		<content:encoded><![CDATA[<p>I have an English degree plus a Master&#8217;s Degree in Lib Science.  I&#8217;ve writen a lot of stuff in college, but don&#8217;t know what happened to it since.  What can I do to show the employers that I have what it takes to be a Tech Writer?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Technical Writing Careers &#8212; Answering 13 Questions about Technical Writing Jobs &#124; I'd Rather Be Writing</title>
		<link>http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/comment-page-1/#comment-105054</link>
		<dc:creator>Technical Writing Careers &#8212; Answering 13 Questions about Technical Writing Jobs &#124; I'd Rather Be Writing</dc:creator>
		<pubDate>Sun, 17 Feb 2008 05:49:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/#comment-105054</guid>
		<description>[...] You might also see this post I wrote: &#8220;How to Break into Technical Writing&#8221;  [...]</description>
		<content:encoded><![CDATA[<p>[...] You might also see this post I wrote: &#8220;How to Break into Technical Writing&#8221;  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/comment-page-1/#comment-75690</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 14 Dec 2007 03:13:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/#comment-75690</guid>
		<description>Thanks for dropping me a note. Glad you liked the post.</description>
		<content:encoded><![CDATA[<p>Thanks for dropping me a note. Glad you liked the post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nancy Odell</title>
		<link>http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/comment-page-1/#comment-75359</link>
		<dc:creator>Nancy Odell</dc:creator>
		<pubDate>Thu, 13 Dec 2007 09:11:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/#comment-75359</guid>
		<description>Hey!...I Googled for clemson sc, but found your page about How to Break into Technical Writing...and have to say thanks. nice read.</description>
		<content:encoded><![CDATA[<p>Hey!&#8230;I Googled for clemson sc, but found your page about How to Break into Technical Writing&#8230;and have to say thanks. nice read.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heidi Hansen's blog: Online Portfolio Idea - Great example</title>
		<link>http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/comment-page-1/#comment-35774</link>
		<dc:creator>Heidi Hansen's blog: Online Portfolio Idea - Great example</dc:creator>
		<pubDate>Tue, 12 Jun 2007 14:02:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/#comment-35774</guid>
		<description>[...] would definitely stand out: http://journey.wsj.com/ This also goes along with Tom Johnson&#039;s recent post about how to break into the Technical Communication field. If you whip up a portfolio similar to [...]</description>
		<content:encoded><![CDATA[<p>[...] would definitely stand out: <a href="http://journey.wsj.com/" rel="nofollow">http://journey.wsj.com/</a> This also goes along with Tom Johnson&#8217;s recent post about how to break into the Technical Communication field. If you whip up a portfolio similar to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gordon</title>
		<link>http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/comment-page-1/#comment-32882</link>
		<dc:creator>Gordon</dc:creator>
		<pubDate>Sun, 03 Jun 2007 20:46:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/#comment-32882</guid>
		<description>Get signed up to TechWR mailing list.

I think that&#039;s the only other bit of advice I can think of... nice article, as was Rhonda&#039;s.

Learning how to pitch your knowledge and your ability to learn new skills is key, if you can sell yourself you are halfway there.</description>
		<content:encoded><![CDATA[<p>Get signed up to TechWR mailing list.</p>
<p>I think that&#8217;s the only other bit of advice I can think of&#8230; nice article, as was Rhonda&#8217;s.</p>
<p>Learning how to pitch your knowledge and your ability to learn new skills is key, if you can sell yourself you are halfway there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CabSav</title>
		<link>http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/comment-page-1/#comment-31467</link>
		<dc:creator>CabSav</dc:creator>
		<pubDate>Fri, 01 Jun 2007 10:10:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/#comment-31467</guid>
		<description>T.  
I would echo Tom and Holly here.  Target your job queries initially to the aviation industry.  It has a couple of advantages--easier to break into, as they have said, but you are also going to get you a higher start pay than in other industries.  Not only that, it&#039;s an easier learning curve. Since you know the terminology, etc. you can concentrate more on becoming a better writer and learning the tools.

If you haven&#039;t already got some samples, start putting them together now.  Tom&#039;s suggestion of writing documentation for open source projects is a good one.  It gives you something &#039;real&#039; to write about, rather than just making stuff up, which is hard.  I know when I was interviewing technical writers two very important things to me were the resume itself  and their folio of work, both of which showed the writer could write.

Rhonda said network, and I agree with that too.  Half the jobs I know about are word of mouth. Tell your pilot friends you want to do technical writing.  (After they get over the huh? part and understand what it is, they may mention your name if they know of anyone who is looking for a writer.) Here in Australia the non-networked jobs come mostly through the agencies.  I don&#039;t know what it&#039;s like in the US, but don&#039;t discount them.

If you&#039;re not a good typist, practise.  Touch-type if possible, and get your speed up.

Toolwise, if you know of a common tool used in the Aviation industry (e.g. FrameMaker) I would spend more effort learning  that one first.  I would also learn about MS Word at least template and style level (and revisions).  I confess in the past I have decided not to interview people based on the fact that their resume was manually formatted rather than using styles. (It may be a personal thing, but my thinking at the time was that if they didn&#039;t know how to use styles then they were going to make a mess of the documents.</description>
		<content:encoded><![CDATA[<p>T.<br />
I would echo Tom and Holly here.  Target your job queries initially to the aviation industry.  It has a couple of advantages&#8211;easier to break into, as they have said, but you are also going to get you a higher start pay than in other industries.  Not only that, it&#8217;s an easier learning curve. Since you know the terminology, etc. you can concentrate more on becoming a better writer and learning the tools.</p>
<p>If you haven&#8217;t already got some samples, start putting them together now.  Tom&#8217;s suggestion of writing documentation for open source projects is a good one.  It gives you something &#8216;real&#8217; to write about, rather than just making stuff up, which is hard.  I know when I was interviewing technical writers two very important things to me were the resume itself  and their folio of work, both of which showed the writer could write.</p>
<p>Rhonda said network, and I agree with that too.  Half the jobs I know about are word of mouth. Tell your pilot friends you want to do technical writing.  (After they get over the huh? part and understand what it is, they may mention your name if they know of anyone who is looking for a writer.) Here in Australia the non-networked jobs come mostly through the agencies.  I don&#8217;t know what it&#8217;s like in the US, but don&#8217;t discount them.</p>
<p>If you&#8217;re not a good typist, practise.  Touch-type if possible, and get your speed up.</p>
<p>Toolwise, if you know of a common tool used in the Aviation industry (e.g. FrameMaker) I would spend more effort learning  that one first.  I would also learn about MS Word at least template and style level (and revisions).  I confess in the past I have decided not to interview people based on the fact that their resume was manually formatted rather than using styles. (It may be a personal thing, but my thinking at the time was that if they didn&#8217;t know how to use styles then they were going to make a mess of the documents.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Holly Harkness</title>
		<link>http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/comment-page-1/#comment-30948</link>
		<dc:creator>Holly Harkness</dc:creator>
		<pubDate>Thu, 31 May 2007 16:02:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/2007/05/27/how-to-break-into-technical-writing/#comment-30948</guid>
		<description>Tom, 
If T is a pilot, he might do better writing technical instructions for aviation equipment or something related to that field. I frequently see ads for technical writers requiring industry-specific knowledge. 

Writing about aviation or aeronautics would be the easiest way for T to break into the field. 

I think those of us who primarily write software instruction forget that there is a TON of technical stuff out there that is mechanical, not electronic, and it all needs documentation. 
Holly</description>
		<content:encoded><![CDATA[<p>Tom,<br />
If T is a pilot, he might do better writing technical instructions for aviation equipment or something related to that field. I frequently see ads for technical writers requiring industry-specific knowledge. </p>
<p>Writing about aviation or aeronautics would be the easiest way for T to break into the field. </p>
<p>I think those of us who primarily write software instruction forget that there is a TON of technical stuff out there that is mechanical, not electronic, and it all needs documentation.<br />
Holly</p>
]]></content:encoded>
	</item>
</channel>
</rss>
