<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:series="http://unfoldingneurons.com/"
	>

<channel>
	<title>I&#039;d Rather Be Writing &#187; change</title>
	<atom:link href="http://idratherbewriting.com/tag/change/feed/" rel="self" type="application/rss+xml" />
	<link>http://idratherbewriting.com</link>
	<description>The Latest Trends in Technical Communication</description>
	<lastBuildDate>Fri, 10 Feb 2012 23:59:59 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Will We Still Know Us, Tomorrow?</title>
		<link>http://idratherbewriting.com/2011/05/10/will-we-still-know-us-tomorrow/</link>
		<comments>http://idratherbewriting.com/2011/05/10/will-we-still-know-us-tomorrow/#comments</comments>
		<pubDate>Tue, 10 May 2011 14:04:03 +0000</pubDate>
		<dc:creator>Tom Johnson</dc:creator>
				<category><![CDATA[blog]]></category>
		<category><![CDATA[careers]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[evolution]]></category>

		<guid isPermaLink="false">http://idratherbewriting.com/?p=9268</guid>
		<description><![CDATA[This is a guest post by Michael Hobren. Michael is a technical and &#8220;marcom&#8221; contract writer, as well as a fictional novelist. He resides with his family in the Tampa, Florida area. As a technical writer, I don&#8217;t think my late father ever quite understood what I do for a living. I would try to explain to him what I did, but to no avail. ... <a href="http://idratherbewriting.com/2011/05/10/will-we-still-know-us-tomorrow/">more &#187;</a>]]></description>
			<content:encoded><![CDATA[<div id="attachment_9273" class="wp-caption alignright" style="width: 147px"><a href="http://idratherbewriting.com/wp-content/uploads/2011/05/michael_hobren.jpg"><img class="size-full wp-image-9273" title="Will We Still Know Us, Tomorrow?" src="http://idratherbewriting.com/wp-content/uploads/2011/05/michael_hobren.jpg" alt="Will We Still Know Us, Tomorrow?" width="137" height="166" /></a><p class="wp-caption-text">Michael Hobren</p></div>
<p><em>This is a guest post by Michael Hobren. Michael is a technical and &#8220;marcom&#8221; contract writer, as well as a fictional novelist. He resides with his family in the Tampa, Florida area.</em></p>
<p><a href="http://idratherbewriting.com/wp-content/uploads/2009/04/orangebar.png"><img class="alignnone size-full wp-image-9119" style="border: none;" title="orangebar" src="http://idratherbewriting.com/wp-content/uploads/2009/04/orangebar.png" alt="" width="300" height="3" border="0" /></a></p>
<p>As a technical writer, I don&#8217;t think my late father ever quite understood what I do for a living. I would try to explain to him what I did, but to no avail. Despite my best efforts, my explanations were typically met with dad saying, &#8220;You know, you should go into television, like Dan Rather or one of <em>those</em> guys.&#8221;</p>
<p>I never took my dad&#8217;s remark as a slight, however, but rather understood that — for <em>his</em> generation — the world was a much simpler place. He served for more than 20 years as a cop. In his day you were simply a butcher, a baker or a candlestick maker: easy-to-understand job descriptions.</p>
<p>Beyond the nuts &amp; bolts of what we technical writers do, the tools we use, and the emerging technologies we gallop to keep pace with, I wonder what we will be <em>called</em> within the next 10 years. As things become more specialized and job requirements evolve and are reclassified, I do not think we will be called Technical Writers for much longer. Simply put, this static handle just will not fit the wave of new development that is already upon us which we, as communications professionals, will be tasked to work with.</p>
<p><strong>Rachel Zupek</strong>, writing for <em>CareerBuilder.com</em>, came up with a short list of job titles that did not exist ten years ago: Bloggers, Content Managers, Green Funeral Directors, Interior REdesigners, Patient Advocates, Senior Move Managers, Social Media Specialists, User Experience Analyst, and Virtual Business Service Providers.</p>
<p>According to another article appearing on <em>Monster.com</em>, &#8220;labor-market forecasters believe that tomorrow&#8217;s new jobs will have unfamiliar titles, such as Visualization Specialists, Social Network Analysts, Parenting Counselors, and Corporate Jesters, who will be paid to tell their leaders important truths that they don&#8217;t want to hear.&#8221;</p>
<p>One example of a new job title to emerge in the healthcare field in recent years is that of &#8220;Informatics Coordinator.&#8221; Healthcare ICs – who are typically RNs – work with the resources, devices and methods needed to optimize the acquisition, storage, retrieval and use of information in health and biomedicine. These nurses are <em>nouveau writers</em> who use many of the same tools as technical writers, combined with their background in clinical nursing, to help bring the ever-growing Mt. Everest of healthcare data into some useful focus. The days of nurses sporting white caps and uniforms, taking blood pressures and dispensing medications only, are now a distant memory.</p>
<h2>So What Will Tomorrow&#8217;s Technical Writers Be Called?</h2>
<p>While some of these new, euphemistic terms are already popping up on the job boards – such as Content Managers and Social Media Specialists – we still have a ways to go. So what will technical writers become in the dawning decade? Will this broad job title be phased out to make room for a new, more descriptive title? Two driving forces will foster the need for new job classifications within the next ten years: <strong>specialization</strong> and <strong>education</strong>.</p>
<p>A present-day example of this is how the daily news is reported. Today, large media sources, such as the <em>Wall Street Journal</em>, retain staff writers who hold double degrees in Journalism and Business Administration. When a full-time staffer is unavailable, a &#8220;contributing editor&#8221; is brought in to do the job, e.g., Dr. Richard Besser who regularly reports for <em>ABC News</em> on health-related matters, and former NSA counter-terrorism expert Richard Clarke on matters of national security, just to name two.</p>
<p>The technical writers of tomorrow will need to have backgrounds other than writing and a general Liberal Arts education in order to be knowledgeable and effective. An English or Journalism degree, combined with ancillary training as a Medical Technician, will be a good inroad to writing for the healthcare field. A cross-section of technical writing and Data Processing training will better enable technical writers to interact and contribute within the computer world.</p>
<h2>Enter the &#8216;ZebraComms&#8217;</h2>
<p>Of course there is a down side to becoming multi-discipline <strong>Zebra Communicators</strong> who bear too many stripes. Tomorrow&#8217;s technical writers may find their skill sets too narrowly focused, and consequently jobs that perfectly fit their profiles may be hard to find. Still, the trend toward specialization, and the education needed to stay abreast of new developments, is not going to reverse itself. As former <em>Disney</em> CEO Michael Eisner said, &#8220;When you&#8217;re trying to create things that are new, you have to be prepared to be on the edge of risk.&#8221;</p>
<p>If we continue to remain communications generalists, relying on product SMEs and others to &#8220;tell us&#8221; what needs to be communicated to a well-informed consumer base, then we relegate ourselves to being glorified stenographers with no real understanding of what we are writing about. As we move forward toward the 2020 mark, becoming <strong>ZebraComms</strong> will be the only way that we will be able to stay in the game, and to become valued strategic stakeholders in what we produce for our clients and employers. Of one thing we can be sure of, even now: time (and technology) waits for no one.<br />
<h2>Blog Sponsors</h2>
<ul>
<li><a href="http://webworks.com">Webworks ePublisher</a></li>
<li><a href="http://scriptorium.com">Scriptorium</a></li>
<li><a href="http://www.helpgenerator.com">Help Generator help authoring software</a></li>
<li><a href="http://idc.spsu.edu">Southern Polytechnic: Information Design and Communication</a></li>
<li><a href="http://simplifiedenglish.net">Simplified English</a></li>
<li><a href="http://info.mindtouch.com/irbw/tcs-custom-tour?persona=content">MindTouch</a></li>
<li><a href="http://www.madcapsoftware.com/products/madpak/overview.aspx?utm_source=IdRatherBeWriting&#038;utm_medium=Banner&#038;utm_campaign=MadPak"</a>Madcap Software</a></li>
<li><a href="http://www.drexplain.com/">Dr.Explain</a> </li>
<li><a href="http://www.adobe.com/products/technicalcommunicationsuite/try.html?sdid=ITRSO">Adobe Technical Communication Suite</a></li>
<li><a href="http://www.congree.com/en/download-congree-personal-edition.aspx">Congree</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://idratherbewriting.com/2011/05/10/will-we-still-know-us-tomorrow/feed/</wfw:commentRss>
		<slash:comments>44</slash:comments>
		</item>
		<item>
		<title>The Do-It-Yourself Philosophy: Saul Carliner at the STC Summit in Dallas, #stc10</title>
		<link>http://idratherbewriting.com/2010/05/09/the-do-it-yourself-philosophy-saul-carliner-at-the-stc-summit-in-dallas/</link>
		<comments>http://idratherbewriting.com/2010/05/09/the-do-it-yourself-philosophy-saul-carliner-at-the-stc-summit-in-dallas/#comments</comments>
		<pubDate>Mon, 10 May 2010 04:07:55 +0000</pubDate>
		<dc:creator>Tom Johnson</dc:creator>
				<category><![CDATA[blog]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[do it yourself]]></category>
		<category><![CDATA[roles]]></category>
		<category><![CDATA[saul carliner]]></category>
		<category><![CDATA[Screencasts]]></category>
		<category><![CDATA[STC Summit]]></category>
		<category><![CDATA[STC Summit in Dallas]]></category>

		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=6262</guid>
		<description><![CDATA[In this video, I interview Saul Carliner about a post he wrote on his blog describing the &#8220;do-it-yourself&#8221; philosophy and whether this philosophy is something technical communicators should embrace or fear. Blog Sponsors Webworks ePublisher Scriptorium Help Generator help authoring software Southern Polytechnic: Information Design and Communication Simplified English MindTouch]]></description>
			<content:encoded><![CDATA[<p>In this video, I interview <a href="http://saulcarliner.blogspot.com" title="Saul Carliner's blog">Saul Carliner</a> about a post he wrote on his blog <a href="http://saulcarliner.blogspot.com/2010/01/do-it-yourself-now-its-management.html">describing the &#8220;do-it-yourself&#8221; philosophy</a> and whether this philosophy is something technical communicators should embrace or fear. </p>
<p><iframe title="YouTube video player" class="youtube-player" type="text/html" width="425" height="344" src="http://www.youtube.com/embed/QAkDQt0_1Zo" frameborder="0" allowFullScreen="true"> </iframe><br />
<h2>Blog Sponsors</h2>
<ul>
<li><a href="http://webworks.com">Webworks ePublisher</a></li>
<li><a href="http://scriptorium.com">Scriptorium</a></li>
<li><a href="http://www.helpgenerator.com">Help Generator help authoring software</a></li>
<li><a href="http://idc.spsu.edu">Southern Polytechnic: Information Design and Communication</a></li>
<li><a href="http://simplifiedenglish.net">Simplified English</a></li>
<li><a href="http://info.mindtouch.com/irbw/tcs-custom-tour?persona=content">MindTouch</a></li>
<li><a href="http://www.madcapsoftware.com/products/madpak/overview.aspx?utm_source=IdRatherBeWriting&#038;utm_medium=Banner&#038;utm_campaign=MadPak"</a>Madcap Software</a></li>
<li><a href="http://www.drexplain.com/">Dr.Explain</a> </li>
<li><a href="http://www.adobe.com/products/technicalcommunicationsuite/try.html?sdid=ITRSO">Adobe Technical Communication Suite</a></li>
<li><a href="http://www.congree.com/en/download-congree-personal-edition.aspx">Congree</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://idratherbewriting.com/2010/05/09/the-do-it-yourself-philosophy-saul-carliner-at-the-stc-summit-in-dallas/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<series:name><![CDATA[STC Summit in Dallas]]></series:name>
	</item>
		<item>
		<title>The Turnaround Screencast</title>
		<link>http://idratherbewriting.com/2010/01/19/the-turnaround-screencast/</link>
		<comments>http://idratherbewriting.com/2010/01/19/the-turnaround-screencast/#comments</comments>
		<pubDate>Tue, 19 Jan 2010 06:31:13 +0000</pubDate>
		<dc:creator>Tom Johnson</dc:creator>
				<category><![CDATA[blog]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[kristi leach]]></category>
		<category><![CDATA[Screencasting]]></category>
		<category><![CDATA[story]]></category>

		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=5583</guid>
		<description><![CDATA[In Screencasts: So what?, Kristi Leach tells an engaging story about a turnaround screencast. She explains how one good screencast can change users&#8217; attitudes about software. Here&#8217;s an excerpt: I rarely watch video online. Unless it’s a funny meme I have deliberately searched for, or a show that I missed, or Netflix, I won’t press play. If a blog post is all video, I skip ... <a href="http://idratherbewriting.com/2010/01/19/the-turnaround-screencast/">more &#187;</a>]]></description>
			<content:encoded><![CDATA[<p>In <a href="http://kwritenow.wordpress.com/2010/01/14/screencasts-so-what/" target="_blank">Screencasts: So what?</a>, Kristi Leach tells an engaging story about a turnaround screencast. She explains how one good screencast can change users&#8217; attitudes about software. Here&#8217;s an excerpt:</p>
<blockquote><p>I rarely watch video online. Unless it’s a funny meme I have deliberately searched for, or a show that I missed, or Netflix, I won’t press play. If a blog post is all video, I skip it. I rarely appreciate video instructions, either–they take too long, because I’m pausing, following the step, playing, pausing again. I was having trouble imagining how videos were going to improve our help systems or fit into our schedules.</p></blockquote>
<p>
<h2>Blog Sponsors</h2>
<ul>
<li><a href="http://webworks.com">Webworks ePublisher</a></li>
<li><a href="http://scriptorium.com">Scriptorium</a></li>
<li><a href="http://www.helpgenerator.com">Help Generator help authoring software</a></li>
<li><a href="http://idc.spsu.edu">Southern Polytechnic: Information Design and Communication</a></li>
<li><a href="http://simplifiedenglish.net">Simplified English</a></li>
<li><a href="http://info.mindtouch.com/irbw/tcs-custom-tour?persona=content">MindTouch</a></li>
<li><a href="http://www.madcapsoftware.com/products/madpak/overview.aspx?utm_source=IdRatherBeWriting&#038;utm_medium=Banner&#038;utm_campaign=MadPak"</a>Madcap Software</a></li>
<li><a href="http://www.drexplain.com/">Dr.Explain</a> </li>
<li><a href="http://www.adobe.com/products/technicalcommunicationsuite/try.html?sdid=ITRSO">Adobe Technical Communication Suite</a></li>
<li><a href="http://www.congree.com/en/download-congree-personal-edition.aspx">Congree</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://idratherbewriting.com/2010/01/19/the-turnaround-screencast/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Identity and Authority. Why the Foundation of Documentation is Changing. &#124; The LugIron Software Blog</title>
		<link>http://idratherbewriting.com/2009/06/22/identity-and-authority-why-the-foundation-of-documentation-is-changing-the-lugiron-software-blog/</link>
		<comments>http://idratherbewriting.com/2009/06/22/identity-and-authority-why-the-foundation-of-documentation-is-changing-the-lugiron-software-blog/#comments</comments>
		<pubDate>Tue, 23 Jun 2009 04:37:50 +0000</pubDate>
		<dc:creator>Tom Johnson</dc:creator>
				<category><![CDATA[change]]></category>
		<category><![CDATA[collaboration]]></category>
		<category><![CDATA[Notes]]></category>
		<category><![CDATA[trends]]></category>

		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=3868</guid>
		<description><![CDATA[Identity and Authority. Why the Foundation of Documentation is Changing. &#124; The LugIron Software Blog. In this post, LugIron says documentation departments now have competition from other sources, whereas previously they dominated this arena without challenges from other sources. He pulls together several posts by various bloggers and suggests a trend in the industry. He ends by arguing, &#8220;This shift [in the tech comm industry] ... <a href="http://idratherbewriting.com/2009/06/22/identity-and-authority-why-the-foundation-of-documentation-is-changing-the-lugiron-software-blog/">more &#187;</a>]]></description>
			<content:encoded><![CDATA[<p><a href="http://blog.lugiron.com/2009/06/identity-and-authority-why-the-foundation-of-documentation-is-changing/">Identity and Authority. Why the Foundation of Documentation is Changing. | The LugIron Software Blog</a>. In this post, LugIron says documentation departments now have competition from other sources, whereas previously they dominated this arena without challenges from other sources. He pulls together several posts by various bloggers and suggests a trend in the industry. He ends by arguing, &#8220;This shift [in the tech comm industry] will be dominated by multi-channel publishing of single-sourced, collaborative content that works to engage and bring users into communities influenced by the company’s they orbit around.<br />
<h2>Blog Sponsors</h2>
<ul>
<li><a href="http://webworks.com">Webworks ePublisher</a></li>
<li><a href="http://scriptorium.com">Scriptorium</a></li>
<li><a href="http://www.helpgenerator.com">Help Generator help authoring software</a></li>
<li><a href="http://idc.spsu.edu">Southern Polytechnic: Information Design and Communication</a></li>
<li><a href="http://simplifiedenglish.net">Simplified English</a></li>
<li><a href="http://info.mindtouch.com/irbw/tcs-custom-tour?persona=content">MindTouch</a></li>
<li><a href="http://www.madcapsoftware.com/products/madpak/overview.aspx?utm_source=IdRatherBeWriting&#038;utm_medium=Banner&#038;utm_campaign=MadPak"</a>Madcap Software</a></li>
<li><a href="http://www.drexplain.com/">Dr.Explain</a> </li>
<li><a href="http://www.adobe.com/products/technicalcommunicationsuite/try.html?sdid=ITRSO">Adobe Technical Communication Suite</a></li>
<li><a href="http://www.congree.com/en/download-congree-personal-edition.aspx">Congree</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://idratherbewriting.com/2009/06/22/identity-and-authority-why-the-foundation-of-documentation-is-changing-the-lugiron-software-blog/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ten Technical Writing Stereotypes</title>
		<link>http://idratherbewriting.com/2008/09/28/ten-technical-writing-stereotypes/</link>
		<comments>http://idratherbewriting.com/2008/09/28/ten-technical-writing-stereotypes/#comments</comments>
		<pubDate>Sun, 28 Sep 2008 18:13:39 +0000</pubDate>
		<dc:creator>Tom Johnson</dc:creator>
				<category><![CDATA[blog]]></category>
		<category><![CDATA[boring]]></category>
		<category><![CDATA[change]]></category>
		<category><![CDATA[Creativity]]></category>
		<category><![CDATA[geek]]></category>
		<category><![CDATA[introversion]]></category>
		<category><![CDATA[myths]]></category>
		<category><![CDATA[second-class citizen]]></category>
		<category><![CDATA[sellout]]></category>
		<category><![CDATA[stereotypes]]></category>
		<category><![CDATA[TechCraft]]></category>
		<category><![CDATA[Technical Writing]]></category>
		<category><![CDATA[technical writing careers]]></category>
		<category><![CDATA[tools]]></category>

		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=2042</guid>
		<description><![CDATA[As college students contemplate careers in technical writing, they often hesitate because of negative stereotypes about the profession. As with many stereotypes, these aspects of technical writing can describe some situations for some people, but as a whole they aren&#8217;t necessarily true. I&#8217;ve listed Ten Technical Writing Stereotypes &#8212; tell me if the stereotypes hold generally true for you or not. You can take the ... <a href="http://idratherbewriting.com/2008/09/28/ten-technical-writing-stereotypes/">more &#187;</a>]]></description>
			<content:encoded><![CDATA[<p>As college students contemplate careers in technical writing, they often hesitate because of negative stereotypes about the profession. As with many stereotypes, these aspects of technical writing can describe some situations for some people, but as a whole they aren&#8217;t necessarily true.</p>
<p>I&#8217;ve listed Ten Technical Writing Stereotypes  &#8212; tell me if the stereotypes hold generally true for you or not. You can take the survey here: <a href="http://www.surveygizmo.com/s/70615/stereotypes">http://www.surveygizmo.com/s/70615/stereotypes</a><span style="color: #004bb5;"><strong>. </strong></span>Additionally, you can respond in the comments below this post.</p>
<p>Update: You can <a href="http://www.idratherbewriting.com/2008/10/08/results-for-my-10-technical-writing-stereo-types-survey/">view the Survey Results here</a>.<span id="more-2042"></span></p>
<h3>1. Technical writing is boring.</h3>
<p>Technical writing is a generally boring activity, involving repetitive, structured writing that requires the same types of sentences over and over (click this, select that, choose this, press that). You spend a good part of your day yawning, editing the same lifeless instructional material while looking out your window and yearning for something more. <em>True or False?</em></p>
<h3>2. Technical writing stifles your creativity.</h3>
<p>Because you spend all day immersed in writing instructional text, your own sense of creativity declines. You feel fewer flashes of inspiration and generally have less creative drive and desire. You even find yourself adopting the same techniques of writing short, clear, dry, humorless sentences in your email and journal. <em>True or False?</em></p>
<h3>3. You do a lot of writing as a technical writer.</h3>
<p>Although your day is punctuated by a meeting here and there, you spend the majority of your day in writing mode &#8212; writing how to use a particular product, or editing what you&#8217;ve written. After a full day at work, your fingerpads are often sore from so much typing! <em>True or False?</em></p>
<h3>4. You need a job in technical communication to get a job in technical communication.</h3>
<p>Breaking into the field of technical communication is a Catch 22: You need a job in technical communication to get a job in technical communication. Sometimes a degree, certificate, or internship in technical writing can make up for a lack of job experience, but generally breaking into technical communication requires job experience in the same field, making it nearly impossible to get in. <em>True or False?</em></p>
<h3>5. Technical writers are second-class citizens in IT departments.</h3>
<p>As a technical writer, you&#8217;re generally treated poorly in IT departments &#8212; ignored in meetings, put in your place when you speak up, avoided by subject matter experts, excluded from decision-making processes, and sometimes given demeaning secretarial tasks. <em>True or False?</em></p>
<h3>6. Technical writers feel as if they&#8217;ve sold out.</h3>
<p>You once aspired to write a novel or go into publishing, but due to financial obstacles, you had to embrace technical writing to meet your monthly bills. You often feel as if you&#8217;re expending your talents in the wrong direction. You&#8217;ve given up on your literary publishing dreams and have resorted to manual-writing as almost your exclusive writing activity. As a writer who once turned heads with your creative prose, you now feel as if you&#8217;ve sold out. <em>True or False?</em></p>
<h3>7. You can easily support a family with other writing careers outside of technical writing.</h3>
<p>You could pursue a variety of careers in writing to support your family in a comfortable way. Whether working as an editor in a publishing house, a journalist at a newspaper, a staff writer for a magazine, a proofreader for a journal, a writing teacher at a university or high school, you can make enough to be the sole breadwinner of your family. <em>True or False?</em></p>
<h3>8. You have to know a lot of tools to break into technical communication.</h3>
<p>To be a competitive applicant for a technical communication job, you need to know a plethora of tools &#8212; RoboHelp, Flare, Framemaker, AuthorIt, InDesign, Visio, Dreamweaver, Photoshop, Paint Shop Pro, Camtasia, Captivate, Word, and a handful of others. You also often have to be familiar with various technologies &#8212; HTML, XML, DITA, Javascript, CSS, RSS, Java, and C++. The tool/technical knowledge for entry can be formidable. <em>True or False?</em></p>
<h3>9. Technical writers are introverted, isolated, boring geeks.</h3>
<p>As a technical writer, you have a generally introverted personality. You keep to yourself most of the day, don&#8217;t enjoy large social gatherings, and spend half your day practically mute. You work in your cube or designated area, typing away solemnly at your computer while others interact around you. You tend to have a lot of arcane, geeky knowledge about things no one else cares about. <em>True or False? </em></p>
<h3>10. Because IT technologies change so frequently, you have to spend large amounts of your spare time just keeping up with what&#8217;s new.</h3>
<p>Your workday ends at 5 p.m., but since the field of IT is moving so quickly, with new sites, applications, and technologies emerging almost daily, you have to spend a good chunk of your spare time at home just keeping up. At times you can feel as if you&#8217;re drowning in new knowledge, barely keeping your head above water. You have little time for anything else. <em>True or False?</em></p>
<p><strong>Note: </strong>This article was originally published in the <a href="http://groups.yahoo.com/group/technical_writers_india/files/TechCraft/" target="_blank">Sept 2008 (Fall) issue of the TechCraft newsletter</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://idratherbewriting.com/2008/09/28/ten-technical-writing-stereotypes/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
	</channel>
</rss>

