<?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: 12 Ways to Write Terrible Documentation</title>
	<atom:link href="http://www.poewar.com/12-ways-to-write-terrible-documentation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.poewar.com/12-ways-to-write-terrible-documentation/</link>
	<description>Writing Career Center</description>
	<lastBuildDate>Sat, 20 Mar 2010 01:51:48 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ewan Kennedy</title>
		<link>http://www.poewar.com/12-ways-to-write-terrible-documentation/comment-page-1/#comment-219682</link>
		<dc:creator>Ewan Kennedy</dc:creator>
		<pubDate>Thu, 18 Sep 2008 15:37:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.poewar.com/12-ways-to-write-terrible-documentation/#comment-219682</guid>
		<description>John,

I just thought I would acknowledge that this article inspired one that I have just completed and named &quot;How to Do Terrible SEO&quot;. It can be found at:

http://www.ehow.com/how_4515101_do-terrible-seo.html

I had as much fun writing it as I did reading yours. Thanks again.</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>I just thought I would acknowledge that this article inspired one that I have just completed and named &#8220;How to Do Terrible SEO&#8221;. It can be found at:</p>
<p><a href="http://www.ehow.com/how_4515101_do-terrible-seo.html" rel="nofollow">http://www.ehow.com/how_4515101_do-terrible-seo.html</a></p>
<p>I had as much fun writing it as I did reading yours. Thanks again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bogdan Radu</title>
		<link>http://www.poewar.com/12-ways-to-write-terrible-documentation/comment-page-1/#comment-219488</link>
		<dc:creator>Bogdan Radu</dc:creator>
		<pubDate>Tue, 09 Sep 2008 15:00:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.poewar.com/12-ways-to-write-terrible-documentation/#comment-219488</guid>
		<description>I’m showing this to my parents. Very funny!

Bogdan Radus last blog post..&lt;a href=&quot;http://www.funnystuffplace.com/wedding-prank-fun/&quot; rel=&quot;nofollow&quot;&gt;wedding prank fun&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I’m showing this to my parents. Very funny!</p>
<p>Bogdan Radus last blog post..<a href="http://www.funnystuffplace.com/wedding-prank-fun/" rel="nofollow">wedding prank fun</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Free Fitness Tips</title>
		<link>http://www.poewar.com/12-ways-to-write-terrible-documentation/comment-page-1/#comment-218093</link>
		<dc:creator>Free Fitness Tips</dc:creator>
		<pubDate>Tue, 02 Sep 2008 18:23:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.poewar.com/12-ways-to-write-terrible-documentation/#comment-218093</guid>
		<description>Learning is a lifetime process. It never ends. 

For a writer, or any professional for that purpose, I&#039;d say that outlining and sketching a general map of what their plans are is quite necessary. Not only in short term, it helps in the long run as well.</description>
		<content:encoded><![CDATA[<p>Learning is a lifetime process. It never ends. </p>
<p>For a writer, or any professional for that purpose, I&#8217;d say that outlining and sketching a general map of what their plans are is quite necessary. Not only in short term, it helps in the long run as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: services à domicile</title>
		<link>http://www.poewar.com/12-ways-to-write-terrible-documentation/comment-page-1/#comment-214742</link>
		<dc:creator>services à domicile</dc:creator>
		<pubDate>Mon, 25 Aug 2008 09:38:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.poewar.com/12-ways-to-write-terrible-documentation/#comment-214742</guid>
		<description>This is great. I do have to write a lot for my website and I love your advices.
Revisions are for suckers... yeah....

services à domiciles last blog post..&lt;a href=&quot;http://blog.aladom.fr/2008/07/12/conseils-pour-ceux-qui-proposent-leurs-services-a-domicile/&quot; rel=&quot;nofollow&quot;&gt;Conseils pour ceux qui proposent leurs services à domicile&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>This is great. I do have to write a lot for my website and I love your advices.<br />
Revisions are for suckers&#8230; yeah&#8230;.</p>
<p>services à domiciles last blog post..<a href="http://blog.aladom.fr/2008/07/12/conseils-pour-ceux-qui-proposent-leurs-services-a-domicile/" rel="nofollow">Conseils pour ceux qui proposent leurs services à domicile</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason P.</title>
		<link>http://www.poewar.com/12-ways-to-write-terrible-documentation/comment-page-1/#comment-210516</link>
		<dc:creator>Jason P.</dc:creator>
		<pubDate>Sat, 16 Aug 2008 15:47:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.poewar.com/12-ways-to-write-terrible-documentation/#comment-210516</guid>
		<description>Funny and helpful too. I need the help more than the comedy, though it works today, as at least 1 of 3 blogs get updated. (Not the one I left either.)

Anywho, Shanghai thought yours was funny. I do too.</description>
		<content:encoded><![CDATA[<p>Funny and helpful too. I need the help more than the comedy, though it works today, as at least 1 of 3 blogs get updated. (Not the one I left either.)</p>
<p>Anywho, Shanghai thought yours was funny. I do too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nkog</title>
		<link>http://www.poewar.com/12-ways-to-write-terrible-documentation/comment-page-1/#comment-208099</link>
		<dc:creator>nkog</dc:creator>
		<pubDate>Sun, 10 Aug 2008 06:35:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.poewar.com/12-ways-to-write-terrible-documentation/#comment-208099</guid>
		<description>Yea it really does depend on the company but I would say most really dont care!

http://hiphopthugz.com</description>
		<content:encoded><![CDATA[<p>Yea it really does depend on the company but I would say most really dont care!</p>
<p><a href="http://hiphopthugz.com" rel="nofollow">http://hiphopthugz.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Hewitt</title>
		<link>http://www.poewar.com/12-ways-to-write-terrible-documentation/comment-page-1/#comment-207724</link>
		<dc:creator>John Hewitt</dc:creator>
		<pubDate>Fri, 08 Aug 2008 21:36:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.poewar.com/12-ways-to-write-terrible-documentation/#comment-207724</guid>
		<description>@ Dave,

It depends on the company, but there are plenty of them that think that way. I will say that Intuit had some nice tools that allowed them to track the success or failure of their documentation based on the decrease in tech support calls after a problem was addressed in the online help. I always respected that about them.</description>
		<content:encoded><![CDATA[<p>@ Dave,</p>
<p>It depends on the company, but there are plenty of them that think that way. I will say that Intuit had some nice tools that allowed them to track the success or failure of their documentation based on the decrease in tech support calls after a problem was addressed in the online help. I always respected that about them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.poewar.com/12-ways-to-write-terrible-documentation/comment-page-1/#comment-207709</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Fri, 08 Aug 2008 20:38:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.poewar.com/12-ways-to-write-terrible-documentation/#comment-207709</guid>
		<description>The reality is that software vendors would love to put out no documentation at all. Documentation is a market barrier intended by large vendors to keep small software companies from doing business. 

I know of no software companies that understand that documentation, training, and technical support are what sells future releases. If they understood this, they could pay for documentation out of the savings inherent in selling to their install base. 

Ultimately, we document and teach, because the developer did not learn from the potential customers or clients, and relied on requirements and a requirements elicitation process that gurantees the delivery of average functionality. That average functionality results from political tradeoffs, so the software fits no one in particular. Somehow we are supposed to make up for that. If the requirements were specific to the individual, no manual would be needed. 

Developers abstract away from requirements, and we have to explicate back to the requirements. So many of the tasks a user must perform has nothing to do with the work they are trying to finish or the artifact that they are trying to create.</description>
		<content:encoded><![CDATA[<p>The reality is that software vendors would love to put out no documentation at all. Documentation is a market barrier intended by large vendors to keep small software companies from doing business. </p>
<p>I know of no software companies that understand that documentation, training, and technical support are what sells future releases. If they understood this, they could pay for documentation out of the savings inherent in selling to their install base. </p>
<p>Ultimately, we document and teach, because the developer did not learn from the potential customers or clients, and relied on requirements and a requirements elicitation process that gurantees the delivery of average functionality. That average functionality results from political tradeoffs, so the software fits no one in particular. Somehow we are supposed to make up for that. If the requirements were specific to the individual, no manual would be needed. </p>
<p>Developers abstract away from requirements, and we have to explicate back to the requirements. So many of the tasks a user must perform has nothing to do with the work they are trying to finish or the artifact that they are trying to create.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dave directory</title>
		<link>http://www.poewar.com/12-ways-to-write-terrible-documentation/comment-page-1/#comment-207068</link>
		<dc:creator>dave directory</dc:creator>
		<pubDate>Thu, 07 Aug 2008 11:43:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.poewar.com/12-ways-to-write-terrible-documentation/#comment-207068</guid>
		<description>Good Article,It&#039;s very useful for me!</description>
		<content:encoded><![CDATA[<p>Good Article,It&#8217;s very useful for me!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Katie</title>
		<link>http://www.poewar.com/12-ways-to-write-terrible-documentation/comment-page-1/#comment-206893</link>
		<dc:creator>Katie</dc:creator>
		<pubDate>Thu, 07 Aug 2008 02:08:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.poewar.com/12-ways-to-write-terrible-documentation/#comment-206893</guid>
		<description>thanks for the tips. but &quot;Revisions are for suckers&quot; i dont no about that.

keep up the good work</description>
		<content:encoded><![CDATA[<p>thanks for the tips. but &#8220;Revisions are for suckers&#8221; i dont no about that.</p>
<p>keep up the good work</p>
]]></content:encoded>
	</item>
</channel>
</rss>
