<?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: An Otherwise Good Experience Soured by Flawed Documentation</title>
	<atom:link href="http://www.gryphonmountain.net/2009/07/an-otherwise-good-experience-soured-by-flawed-documentation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gryphonmountain.net/2009/07/an-otherwise-good-experience-soured-by-flawed-documentation/</link>
	<description>Technical Communication and Other Writing Topics, by Ben Minson</description>
	<lastBuildDate>Wed, 11 Jan 2012 04:05:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Mike Starr</title>
		<link>http://www.gryphonmountain.net/2009/07/an-otherwise-good-experience-soured-by-flawed-documentation/#comment-333</link>
		<dc:creator>Mike Starr</dc:creator>
		<pubDate>Wed, 24 Mar 2010 13:49:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.gryphonmountain.net/?p=648#comment-333</guid>
		<description>More likely the case in this example is that the technical writer was *not allowed* to provide good documentation.</description>
		<content:encoded><![CDATA[<p>More likely the case in this example is that the technical writer was *not allowed* to provide good documentation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://www.gryphonmountain.net/2009/07/an-otherwise-good-experience-soured-by-flawed-documentation/#comment-332</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Tue, 14 Jul 2009 00:48:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.gryphonmountain.net/?p=648#comment-332</guid>
		<description>Sheila, your comment addresses a topic I&#039;ve been thinking about: the use of examples.</description>
		<content:encoded><![CDATA[<p>Sheila, your comment addresses a topic I&#8217;ve been thinking about: the use of examples.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sheila Loring</title>
		<link>http://www.gryphonmountain.net/2009/07/an-otherwise-good-experience-soured-by-flawed-documentation/#comment-331</link>
		<dc:creator>Sheila Loring</dc:creator>
		<pubDate>Thu, 09 Jul 2009 20:32:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.gryphonmountain.net/?p=648#comment-331</guid>
		<description>I have to put a plug in for Madcap Flare documentation. Examples are provided for each task, and they&#039;re realistic. In fact, I&#039;ve been in many a quandry that the examples addressed.

Some of the help pages are fairly long, but readability is increased by sections you can collapse and expand.</description>
		<content:encoded><![CDATA[<p>I have to put a plug in for Madcap Flare documentation. Examples are provided for each task, and they&#8217;re realistic. In fact, I&#8217;ve been in many a quandry that the examples addressed.</p>
<p>Some of the help pages are fairly long, but readability is increased by sections you can collapse and expand.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Margherite</title>
		<link>http://www.gryphonmountain.net/2009/07/an-otherwise-good-experience-soured-by-flawed-documentation/#comment-330</link>
		<dc:creator>Margherite</dc:creator>
		<pubDate>Thu, 09 Jul 2009 18:57:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.gryphonmountain.net/?p=648#comment-330</guid>
		<description>Add to the list - no indication that the engineers or marketers knew how the customers were likely to use the device. The scary inference is that the router was designed without a set of use cases, and the problems go much deeper within D-Link&#039;s corporate psyche than a problem with technical communication.</description>
		<content:encoded><![CDATA[<p>Add to the list &#8211; no indication that the engineers or marketers knew how the customers were likely to use the device. The scary inference is that the router was designed without a set of use cases, and the problems go much deeper within D-Link&#8217;s corporate psyche than a problem with technical communication.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

