<?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/"
	>

<channel>
	<title>In My Opinion</title>
	<atom:link href="http://blog.afour.co.za/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://blog.afour.co.za</link>
	<description>Musings of a Technical Writer and other stories</description>
	<lastBuildDate>Mon, 05 Dec 2011 19:08:25 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>Who wants to be a millionaire?</title>
		<link>http://blog.afour.co.za/?p=324</link>
		<comments>http://blog.afour.co.za/?p=324#comments</comments>
		<pubDate>Mon, 05 Dec 2011 18:46:00 +0000</pubDate>
		<dc:creator>alanandrew</dc:creator>
				<category><![CDATA[Humour]]></category>

		<guid isPermaLink="false">http://blog.afour.co.za/?p=324</guid>
		<description><![CDATA[&#160; To become a millionaire is easy — all you need to do is decide! &#8230; and this is how you do it. Thanks to and courtesy of Bill Watterson]]></description>
		<wfw:commentRss>http://blog.afour.co.za/?feed=rss2&#038;p=324</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is a typical technical writing methodology?</title>
		<link>http://blog.afour.co.za/?p=299</link>
		<comments>http://blog.afour.co.za/?p=299#comments</comments>
		<pubDate>Sun, 14 Aug 2011 09:04:45 +0000</pubDate>
		<dc:creator>alanandrew</dc:creator>
				<category><![CDATA[Technical Writing]]></category>

		<guid isPermaLink="false">http://blog.afour.co.za/?p=299</guid>
		<description><![CDATA[To create a technical document, a technical writer must understand the audience and purpose. The writer gathers information by studying existing material and interviewing SMEs. The technical writer also studies the audience to learn their needs and technical understanding level. Well-formed technical documents follow common publishing guidelines. Technical documentation comes in many styles and formats, [...]]]></description>
		<wfw:commentRss>http://blog.afour.co.za/?feed=rss2&#038;p=299</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Which Skill Sets are Important?</title>
		<link>http://blog.afour.co.za/?p=281</link>
		<comments>http://blog.afour.co.za/?p=281#comments</comments>
		<pubDate>Sun, 14 Aug 2011 08:50:24 +0000</pubDate>
		<dc:creator>alanandrew</dc:creator>
				<category><![CDATA[Technical Writing]]></category>

		<guid isPermaLink="false">http://blog.afour.co.za/?p=281</guid>
		<description><![CDATA[Like any profession, becoming a technical writer requires a mastery of a certain set of skills. This skill set used to involve primarily writing and illustration skills, as large manuals for print publication were the standard in the profession. The worlds of communications and technology have evolved dramatically in the latter part of the 20th [...]]]></description>
		<wfw:commentRss>http://blog.afour.co.za/?feed=rss2&#038;p=281</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Painful truths of not using a Technical Writer</title>
		<link>http://blog.afour.co.za/?p=289</link>
		<comments>http://blog.afour.co.za/?p=289#comments</comments>
		<pubDate>Sun, 19 Jun 2011 08:59:11 +0000</pubDate>
		<dc:creator>alanandrew</dc:creator>
				<category><![CDATA[Technical Writing]]></category>

		<guid isPermaLink="false">http://blog.afour.co.za/?p=289</guid>
		<description><![CDATA[Some business managers fail to recognize the impact on profitability of good technical documentation and other support literature, or the lack thereof. You might hear them say—as I have—“It’s not really a priority at the moment” or “We may consider it later” or even &#8220;It cost too much, we&#8217;ll have to do without it&#8221;.  And [...]]]></description>
		<wfw:commentRss>http://blog.afour.co.za/?feed=rss2&#038;p=289</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How Technical Writers Add Value to Your Team</title>
		<link>http://blog.afour.co.za/?p=279</link>
		<comments>http://blog.afour.co.za/?p=279#comments</comments>
		<pubDate>Wed, 18 May 2011 08:49:08 +0000</pubDate>
		<dc:creator>alanandrew</dc:creator>
				<category><![CDATA[Technical Writing]]></category>

		<guid isPermaLink="false">http://blog.afour.co.za/?p=279</guid>
		<description><![CDATA[Technical writers can add a great deal of value to your products or services. They are experienced and trained: Understand the requirements of the information they produce, not only formatting and size requirements and restrictions, but balancing the need to provide adequate useful information against the danger of providing too much information, which can lead [...]]]></description>
		<wfw:commentRss>http://blog.afour.co.za/?feed=rss2&#038;p=279</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Technical Writers are Communicators</title>
		<link>http://blog.afour.co.za/?p=303</link>
		<comments>http://blog.afour.co.za/?p=303#comments</comments>
		<pubDate>Tue, 12 Apr 2011 11:08:05 +0000</pubDate>
		<dc:creator>alanandrew</dc:creator>
				<category><![CDATA[Research]]></category>

		<guid isPermaLink="false">http://blog.afour.co.za/?p=303</guid>
		<description><![CDATA[The Society for Technical Communication (STC), the professional organization for technical writers, is involved in a movement to re-classify technical writers as technical communicators. A similar effort is also underway in the United Kingdom. To some technical writers, this movement is a bit contrary to their self-image as professional writers, while others welcome the change and agree that technical writers [...]]]></description>
		<wfw:commentRss>http://blog.afour.co.za/?feed=rss2&#038;p=303</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Six Emerging Trends in Technical Communication</title>
		<link>http://blog.afour.co.za/?p=275</link>
		<comments>http://blog.afour.co.za/?p=275#comments</comments>
		<pubDate>Wed, 23 Mar 2011 08:45:45 +0000</pubDate>
		<dc:creator>alanandrew</dc:creator>
				<category><![CDATA[Trends]]></category>

		<guid isPermaLink="false">http://blog.afour.co.za/?p=275</guid>
		<description><![CDATA[Wondering where technical communication is headed, in 2010 and beyond? Sarah O’Keefe, Ellis Pratt, and Tony Self offer their insights. According to these respected thought leaders, here are six emerging trends in technical communication: Trend 1: Documentation will become more of a [positive] emotional experience for the user. Trend 2: Technical communicators will start writing [...]]]></description>
		<wfw:commentRss>http://blog.afour.co.za/?feed=rss2&#038;p=275</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is Rapid e-Learning?</title>
		<link>http://blog.afour.co.za/?p=307</link>
		<comments>http://blog.afour.co.za/?p=307#comments</comments>
		<pubDate>Wed, 16 Mar 2011 13:01:18 +0000</pubDate>
		<dc:creator>alanandrew</dc:creator>
				<category><![CDATA[Rapid e-Learning]]></category>

		<guid isPermaLink="false">http://blog.afour.co.za/?p=307</guid>
		<description><![CDATA[There are plenty of definitions regarding Rapid e-Learning. A lot of them are variations of strange theories. But, I have only one definition: &#8220;Rapid e-Learning is the development of learning courseware within a short timeline, which is achieved using basic templates which form a static framework and contains the learning content.&#8221; This implies that not much time is [...]]]></description>
		<wfw:commentRss>http://blog.afour.co.za/?feed=rss2&#038;p=307</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What’s the difference between a technical communicator and a technical writer?</title>
		<link>http://blog.afour.co.za/?p=269</link>
		<comments>http://blog.afour.co.za/?p=269#comments</comments>
		<pubDate>Fri, 31 Dec 2010 10:56:32 +0000</pubDate>
		<dc:creator>alanandrew</dc:creator>
				<category><![CDATA[Third-Party Articles]]></category>

		<guid isPermaLink="false">http://blog.afour.co.za/?p=269</guid>
		<description><![CDATA[According to the United States Department of Labor (DOL), the official description, written years ago, of the technical writer’s responsibilities is the following: “Write technical materials, such as equipment manuals, appendices, or operating and maintenance instructions. May assist in layout work.” Today, communication covers much, much more. STC members do much, much more. Their work [...]]]></description>
		<wfw:commentRss>http://blog.afour.co.za/?feed=rss2&#038;p=269</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The QA of Product Design</title>
		<link>http://blog.afour.co.za/?p=255</link>
		<comments>http://blog.afour.co.za/?p=255#comments</comments>
		<pubDate>Wed, 08 Sep 2010 17:08:36 +0000</pubDate>
		<dc:creator>alanandrew</dc:creator>
				<category><![CDATA[Third-Party Articles]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Quality Assurance]]></category>

		<guid isPermaLink="false">http://blog.afour.co.za/?p=255</guid>
		<description><![CDATA[I bring this article to you courtesy of Gryphon Mountain Journals, as I think it adds enormous pertinence to what we do. You may view the original article here. Technical Communication: The QA of Product Design Friday, August 13th, 2010 In our ongoing department reorganization, we technical writers are experiencing some angst as we carve [...]]]></description>
		<wfw:commentRss>http://blog.afour.co.za/?feed=rss2&#038;p=255</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

