<?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/"
	xmlns:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: Becoming a Writer &#8212; Reflections on a Trip to Idaho</title>
	<atom:link href="http://idratherbewriting.com/2008/10/13/becoming-a-writer-reflections-on-a-trip-to-idaho/feed/" rel="self" type="application/rss+xml" />
	<link>http://idratherbewriting.com/2008/10/13/becoming-a-writer-reflections-on-a-trip-to-idaho/</link>
	<description>The Latest Trends in Technical Communication</description>
	<lastBuildDate>Tue, 14 Feb 2012 08:22:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Franklin Zupancic</title>
		<link>http://idratherbewriting.com/2008/10/13/becoming-a-writer-reflections-on-a-trip-to-idaho/comment-page-1/#comment-159517</link>
		<dc:creator>Franklin Zupancic</dc:creator>
		<pubDate>Thu, 02 Sep 2010 03:30:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=2082#comment-159517</guid>
		<description>I had to read your post three times to get the full meaning of it. I enjoy reading what you have to say. It&#039;s too bad that more people do not understand the benefits of coaching. Keep up the good work.</description>
		<content:encoded><![CDATA[<p>I had to read your post three times to get the full meaning of it. I enjoy reading what you have to say. It&#8217;s too bad that more people do not understand the benefits of coaching. Keep up the good work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Becoming a Writer — Reflections on a Trip to Idaho &#124; I&#39;d Rather Be &#8230; &#124; BYU 411</title>
		<link>http://idratherbewriting.com/2008/10/13/becoming-a-writer-reflections-on-a-trip-to-idaho/comment-page-1/#comment-153311</link>
		<dc:creator>Becoming a Writer — Reflections on a Trip to Idaho &#124; I&#39;d Rather Be &#8230; &#124; BYU 411</dc:creator>
		<pubDate>Sat, 05 Jun 2010 19:12:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=2082#comment-153311</guid>
		<description>[...] Becoming a Writer — Reflections on a Trip to Idaho &#124; I&#039;d Rather Be ...      BYU News feminist literature, phone books, rexburg idaho, teaching literature, technical writers [...]</description>
		<content:encoded><![CDATA[<p>[...] Becoming a Writer — Reflections on a Trip to Idaho | I&#39;d Rather Be &#8230;      BYU News feminist literature, phone books, rexburg idaho, teaching literature, technical writers [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Serge Senna</title>
		<link>http://idratherbewriting.com/2008/10/13/becoming-a-writer-reflections-on-a-trip-to-idaho/comment-page-1/#comment-139506</link>
		<dc:creator>Serge Senna</dc:creator>
		<pubDate>Thu, 16 Apr 2009 21:54:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=2082#comment-139506</guid>
		<description>I found your blog on google and read a few of your other posts.
You have a great Blog!!! I just added you to my Google News Reader. 
Look forward to reading more from you in the future.

Keep up the good work.</description>
		<content:encoded><![CDATA[<p>I found your blog on google and read a few of your other posts.<br />
You have a great Blog!!! I just added you to my Google News Reader.<br />
Look forward to reading more from you in the future.</p>
<p>Keep up the good work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Self Certificate Sickness</title>
		<link>http://idratherbewriting.com/2008/10/13/becoming-a-writer-reflections-on-a-trip-to-idaho/comment-page-1/#comment-137347</link>
		<dc:creator>Self Certificate Sickness</dc:creator>
		<pubDate>Thu, 05 Feb 2009 08:13:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=2082#comment-137347</guid>
		<description>It is a feel-good article for me as an aspiring writer.It gives me some information and backgrounds about what writing is all about.</description>
		<content:encoded><![CDATA[<p>It is a feel-good article for me as an aspiring writer.It gives me some information and backgrounds about what writing is all about.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Voos Baratos</title>
		<link>http://idratherbewriting.com/2008/10/13/becoming-a-writer-reflections-on-a-trip-to-idaho/comment-page-1/#comment-137253</link>
		<dc:creator>Voos Baratos</dc:creator>
		<pubDate>Sat, 31 Jan 2009 19:55:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=2082#comment-137253</guid>
		<description>Thanks for the interesting read! I am not a writer but am looking to write better since I have a website for my job. This gave me some insight on where to begin to be a better writer. Thank you</description>
		<content:encoded><![CDATA[<p>Thanks for the interesting read! I am not a writer but am looking to write better since I have a website for my job. This gave me some insight on where to begin to be a better writer. Thank you</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Pleasure of Language &#8212; Essential Listening for Hyper-corrective Grammarians &#124; I'd Rather Be Writing - Tom Johnson</title>
		<link>http://idratherbewriting.com/2008/10/13/becoming-a-writer-reflections-on-a-trip-to-idaho/comment-page-1/#comment-136796</link>
		<dc:creator>The Pleasure of Language &#8212; Essential Listening for Hyper-corrective Grammarians &#124; I'd Rather Be Writing - Tom Johnson</dc:creator>
		<pubDate>Sat, 03 Jan 2009 16:03:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=2082#comment-136796</guid>
		<description>[...] few months ago I attended a creative writing conference in Idaho in which the keynote speaker spent thirty minutes explaining that, when you become a writer, you [...]</description>
		<content:encoded><![CDATA[<p>[...] few months ago I attended a creative writing conference in Idaho in which the keynote speaker spent thirty minutes explaining that, when you become a writer, you [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kirsty</title>
		<link>http://idratherbewriting.com/2008/10/13/becoming-a-writer-reflections-on-a-trip-to-idaho/comment-page-1/#comment-135490</link>
		<dc:creator>Kirsty</dc:creator>
		<pubDate>Fri, 31 Oct 2008 05:54:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=2082#comment-135490</guid>
		<description>Every now and then, I think I&#039;m one of those weird tech writers. ;) When I left uni, I *wanted* to be a tech writer, but I hadn&#039;t done a degree or even a single subject about tech writing (apart from a stoopid communication for IT engineers subject in my first year of my started-but-not-completed IT degree). I only knew about tech writing because one of truly IT-savvy friends at uni worked in one of the research companies on campus, and he told me about these tech writers who worked there because &quot;they couldn&#039;t be programmers&quot;. 
I&#039;ve never wanted to write fiction, novels, books, or poetry. Now and then I dream of being a travel writer, but shudder at the thought of word limits and what I perceive to be &quot;flowery&quot; writing. 
Granted, when I started uni, I didn&#039;t want to be a tech writer (goodness knows what I did want to be, but it was something involving IT and speaking German), and muddled through a couple of years of IT hell before concluding that I didn&#039;t want to be a programmer, and changing courses to do a BA in Linguistics and Business German. 
I graduated, and a couple of months later met my future-first-boss at a church youth camp. He was looking to hire a grad tech writer, and I was looking to become one! And 9.5 years later, I&#039;m still in tech comm, swimming with my fish.</description>
		<content:encoded><![CDATA[<p>Every now and then, I think I&#8217;m one of those weird tech writers. <img src='http://idratherbewriting.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  When I left uni, I *wanted* to be a tech writer, but I hadn&#8217;t done a degree or even a single subject about tech writing (apart from a stoopid communication for IT engineers subject in my first year of my started-but-not-completed IT degree). I only knew about tech writing because one of truly IT-savvy friends at uni worked in one of the research companies on campus, and he told me about these tech writers who worked there because &#8220;they couldn&#8217;t be programmers&#8221;.<br />
I&#8217;ve never wanted to write fiction, novels, books, or poetry. Now and then I dream of being a travel writer, but shudder at the thought of word limits and what I perceive to be &#8220;flowery&#8221; writing.<br />
Granted, when I started uni, I didn&#8217;t want to be a tech writer (goodness knows what I did want to be, but it was something involving IT and speaking German), and muddled through a couple of years of IT hell before concluding that I didn&#8217;t want to be a programmer, and changing courses to do a BA in Linguistics and Business German.<br />
I graduated, and a couple of months later met my future-first-boss at a church youth camp. He was looking to hire a grad tech writer, and I was looking to become one! And 9.5 years later, I&#8217;m still in tech comm, swimming with my fish.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shannon</title>
		<link>http://idratherbewriting.com/2008/10/13/becoming-a-writer-reflections-on-a-trip-to-idaho/comment-page-1/#comment-135467</link>
		<dc:creator>Shannon</dc:creator>
		<pubDate>Tue, 28 Oct 2008 22:52:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=2082#comment-135467</guid>
		<description>Great post and very timely for me!  I have my BA-English, writing emphasis but I was one of those folks who absolutely was NOT going to end up in technical writing.  I could lay that at the feet of my technical rhetoric professor, but in truth, it had more to do with my hopes of being a fiction editor.

Here it is a long four years after graduation and I&#039;m a graduate student in an LIS program and I&#039;ve discovered that I&#039;m actually interested in technical writing.  I&#039;m kicking myself that I didn&#039;t get that certificate back in my undergrad days, but I&#039;m fine with doing the work on my own so I can get my skill level up.

On the notion of blogging as &quot;performative,&quot; I had never thought of it that way before, but must admit that my extrovert nature does thrive on it.  I love your comment about how the process of writing becomes a self-aware event, as we become conscious of how our audience will view what we have written.

All in all, I&#039;m glad to have found your blog and plan to be a faithful reader as I begin this new direction that has taken me a few years to discover.</description>
		<content:encoded><![CDATA[<p>Great post and very timely for me!  I have my BA-English, writing emphasis but I was one of those folks who absolutely was NOT going to end up in technical writing.  I could lay that at the feet of my technical rhetoric professor, but in truth, it had more to do with my hopes of being a fiction editor.</p>
<p>Here it is a long four years after graduation and I&#8217;m a graduate student in an LIS program and I&#8217;ve discovered that I&#8217;m actually interested in technical writing.  I&#8217;m kicking myself that I didn&#8217;t get that certificate back in my undergrad days, but I&#8217;m fine with doing the work on my own so I can get my skill level up.</p>
<p>On the notion of blogging as &#8220;performative,&#8221; I had never thought of it that way before, but must admit that my extrovert nature does thrive on it.  I love your comment about how the process of writing becomes a self-aware event, as we become conscious of how our audience will view what we have written.</p>
<p>All in all, I&#8217;m glad to have found your blog and plan to be a faithful reader as I begin this new direction that has taken me a few years to discover.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://idratherbewriting.com/2008/10/13/becoming-a-writer-reflections-on-a-trip-to-idaho/comment-page-1/#comment-135388</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Thu, 23 Oct 2008 13:00:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=2082#comment-135388</guid>
		<description>Good post. Like you and some of the other posters, I too &quot;fell&quot; into Technical Writing somewhat by accident.

I was a career soldier, working in Army Intelligence. Contrary to popular novels and movies, an Intelligence Analyst has more in common with your average Technical Writer than with James Bond. I spent about 10 years in the field of Technical Writing before I even realized it existed. Taking bits of information gathered from various sources and compiling them into a coherent, informative report that someone will actually read is not unlike gathering information from SMEs and translating it into a helpful user manual.

While in the service, I was going to college part-time and trying to find a major. Since I was always told I had a gift for writing, I gravitated toward a degree in Communications. It was then that I took my first real course in Technical Writing and discovered that this was an actual career. The instructor was very enthusiastic and for his day job, owned a company whose main line of business was helping Architects get funding by translating their plans into proposals. 

At the same time, the military was creeping into the Information Age, and I was given the task of creating an automated database for our myriad intelligence reports using the new (at the time) dBaseIV. I was given an office with a computer, the software, and a manual the size of a phone book that was obviously written by the developers. Suffice it to say the manual was worse than useless and I ended up teaching myself how to use the software. After completing the task, I reflected on how poorly written the manual was and set about writing my own. It was my first user manual, and my superiors were so impressed, I was given an award. It was then I realized that I could make a living at this.

When I retired from the Army, with a BS in Communications, I thought the corporate world would welcome me with open arms (how naive was I?). It took me six months to land a contract position with an agency - straight hourly rate, no benefits, no vacation, no sick days, and a year working at that job before I found an actual full-time job. 

I lasted one year in that job and left one step ahead of a layoff, landing a better-paying job with a defense contractor and even got a signing bonus! (I thought only programmers and engineers got those.) I lasted there for almost five years and again escaped another layoff due to the company being bought by moving on two weeks before the &quot;Monday Morning Massacre&quot; where 14 of my friends and former co-workers got the axe. At least I got them to pay for my Master&#039;s Degree.

I&#039;ve been in my current job for over three years now. The pay is good, the benefits fantastic (1 for 1 401k match, stock options, telecommuting 4 days a week), but I have to say, the enthusiasm I once felt for Technical Writing has waned a great deal.

In my many Technical Writing jobs, I&#039;ve done everything from prepare a complete documentation set and online help from scratch, to formatting documents written by SMEs. I&#039;ve worked mostly in software and while the pay is still good, the days where I feel anything remotely resembling job satisfaction are few and far between. Maybe it&#039;s the chaotic nature of software - never following a project plan, just in time releases, documentation thrown together at the last minute that never seems like it&#039;s complete.

Anyway, I guess I shouldn&#039;t complain. There are a lot of people with English or Communications degrees that are waiting tables, not to mention a lot of underpaid Tech Writers in my area. 

All in all, I guess this is a good &quot;day job&quot; for someone who wants to be a writer.</description>
		<content:encoded><![CDATA[<p>Good post. Like you and some of the other posters, I too &#8220;fell&#8221; into Technical Writing somewhat by accident.</p>
<p>I was a career soldier, working in Army Intelligence. Contrary to popular novels and movies, an Intelligence Analyst has more in common with your average Technical Writer than with James Bond. I spent about 10 years in the field of Technical Writing before I even realized it existed. Taking bits of information gathered from various sources and compiling them into a coherent, informative report that someone will actually read is not unlike gathering information from SMEs and translating it into a helpful user manual.</p>
<p>While in the service, I was going to college part-time and trying to find a major. Since I was always told I had a gift for writing, I gravitated toward a degree in Communications. It was then that I took my first real course in Technical Writing and discovered that this was an actual career. The instructor was very enthusiastic and for his day job, owned a company whose main line of business was helping Architects get funding by translating their plans into proposals. </p>
<p>At the same time, the military was creeping into the Information Age, and I was given the task of creating an automated database for our myriad intelligence reports using the new (at the time) dBaseIV. I was given an office with a computer, the software, and a manual the size of a phone book that was obviously written by the developers. Suffice it to say the manual was worse than useless and I ended up teaching myself how to use the software. After completing the task, I reflected on how poorly written the manual was and set about writing my own. It was my first user manual, and my superiors were so impressed, I was given an award. It was then I realized that I could make a living at this.</p>
<p>When I retired from the Army, with a BS in Communications, I thought the corporate world would welcome me with open arms (how naive was I?). It took me six months to land a contract position with an agency &#8211; straight hourly rate, no benefits, no vacation, no sick days, and a year working at that job before I found an actual full-time job. </p>
<p>I lasted one year in that job and left one step ahead of a layoff, landing a better-paying job with a defense contractor and even got a signing bonus! (I thought only programmers and engineers got those.) I lasted there for almost five years and again escaped another layoff due to the company being bought by moving on two weeks before the &#8220;Monday Morning Massacre&#8221; where 14 of my friends and former co-workers got the axe. At least I got them to pay for my Master&#8217;s Degree.</p>
<p>I&#8217;ve been in my current job for over three years now. The pay is good, the benefits fantastic (1 for 1 401k match, stock options, telecommuting 4 days a week), but I have to say, the enthusiasm I once felt for Technical Writing has waned a great deal.</p>
<p>In my many Technical Writing jobs, I&#8217;ve done everything from prepare a complete documentation set and online help from scratch, to formatting documents written by SMEs. I&#8217;ve worked mostly in software and while the pay is still good, the days where I feel anything remotely resembling job satisfaction are few and far between. Maybe it&#8217;s the chaotic nature of software &#8211; never following a project plan, just in time releases, documentation thrown together at the last minute that never seems like it&#8217;s complete.</p>
<p>Anyway, I guess I shouldn&#8217;t complain. There are a lot of people with English or Communications degrees that are waiting tables, not to mention a lot of underpaid Tech Writers in my area. </p>
<p>All in all, I guess this is a good &#8220;day job&#8221; for someone who wants to be a writer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How Do I Become A Professional Writer &#124; English Writing Software</title>
		<link>http://idratherbewriting.com/2008/10/13/becoming-a-writer-reflections-on-a-trip-to-idaho/comment-page-1/#comment-135380</link>
		<dc:creator>How Do I Become A Professional Writer &#124; English Writing Software</dc:creator>
		<pubDate>Thu, 23 Oct 2008 06:44:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=2082#comment-135380</guid>
		<description>[...] Becoming a Writer — Reflections on a Trip to Idaho [...]</description>
		<content:encoded><![CDATA[<p>[...] Becoming a Writer — Reflections on a Trip to Idaho [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

