<?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: System Documentation: 10 Recommendations</title>
	<atom:link href="http://greatdocuments.net/system-documentation-10-recommendations/feed/" rel="self" type="application/rss+xml" />
	<link>http://greatdocuments.net/system-documentation-10-recommendations/</link>
	<description>Technical Writing by Keith Johnson</description>
	<lastBuildDate>Tue, 02 Mar 2010 07:40:58 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: website design</title>
		<link>http://greatdocuments.net/system-documentation-10-recommendations/comment-page-1/#comment-60</link>
		<dc:creator>website design</dc:creator>
		<pubDate>Sun, 06 Jul 2008 22:34:11 +0000</pubDate>
		<guid isPermaLink="false">http://greatdocuments.net/?p=73#comment-60</guid>
		<description>Informative article on system documentation.</description>
		<content:encoded><![CDATA[<p>Informative article on system documentation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Johnson</title>
		<link>http://greatdocuments.net/system-documentation-10-recommendations/comment-page-1/#comment-54</link>
		<dc:creator>Keith Johnson</dc:creator>
		<pubDate>Tue, 01 Jul 2008 21:54:54 +0000</pubDate>
		<guid isPermaLink="false">http://greatdocuments.net/?p=73#comment-54</guid>
		<description>Thanks, Arjan, for your comment. It is not easy to code in such a way, always, that favorable documentation is the result. That is why we need to learn XML and also use a good documentation generator to ensure the best possible quality with our system documentation.  Cheers, Keith</description>
		<content:encoded><![CDATA[<p>Thanks, Arjan, for your comment. It is not easy to code in such a way, always, that favorable documentation is the result. That is why we need to learn XML and also use a good documentation generator to ensure the best possible quality with our system documentation.  Cheers, Keith</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arjan`s World &#187; LINKBLOG for June 30, 2008</title>
		<link>http://greatdocuments.net/system-documentation-10-recommendations/comment-page-1/#comment-52</link>
		<dc:creator>Arjan`s World &#187; LINKBLOG for June 30, 2008</dc:creator>
		<pubDate>Mon, 30 Jun 2008 19:29:37 +0000</pubDate>
		<guid isPermaLink="false">http://greatdocuments.net/?p=73#comment-52</guid>
		<description>[...] System Documentation: 10 Recommendations - Keith Johnson &#8216; Many times, programmers understand their own logic when it comes to programming, but cannot seem to understand the thought processes of other programmers &#8216; What I missed was coding in such a way that codes explains itself (less comments==better) [...]</description>
		<content:encoded><![CDATA[<p>[...] System Documentation: 10 Recommendations &#8211; Keith Johnson &#8216; Many times, programmers understand their own logic when it comes to programming, but cannot seem to understand the thought processes of other programmers &#8216; What I missed was coding in such a way that codes explains itself (less comments==better) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
