<?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>red-library.com &#187; documentation</title>
	<atom:link href="http://www.red-library.com/tag/documentation/feed" rel="self" type="application/rss+xml" />
	<link>http://www.red-library.com</link>
	<description>Programming &#38; Web Development</description>
	<lastBuildDate>Mon, 28 Feb 2011 10:55:02 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Why you should read documentation</title>
		<link>http://www.red-library.com/why-you-should-read-documentation-34</link>
		<comments>http://www.red-library.com/why-you-should-read-documentation-34#comments</comments>
		<pubDate>Thu, 28 Jan 2010 16:21:43 +0000</pubDate>
		<dc:creator>Sean</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[documentation]]></category>
		<category><![CDATA[help]]></category>
		<category><![CDATA[programming]]></category>

		<guid isPermaLink="false">http://www.red-library.com/?p=34</guid>
		<description><![CDATA[Something struck me today whilst reading a tweet from a developer I consider to be on top of their game. They had an issue with a framework doing something unexpected and annoying, and after hours of trying to get around it, eventually they had to get a solution. They posted a tweet asking if anyone [...]]]></description>
			<content:encoded><![CDATA[<p>Something struck me today whilst reading a tweet from a developer I consider to be on top of their game. They had an issue with a framework doing something unexpected and annoying, and after hours of trying to get around it, eventually they had to get a solution. They posted a tweet asking if anyone knew the solution as they suspected it would just be something really simple which they didn&#8217;t know.</p>
<p>Helpfully someone responded and pointed them in the right direction, but only then did this developer actually bother to look at the documentation themselves. The solution was simple and was fully documented &#8211; so why not check it out first to alleviate all that bother?</p>
<p>While this is a good example of the value of Twitter, I can&#8217;t help but feel that the documentation should always be your first port of call. I don&#8217;t ask someone until I&#8217;ve checked out the documentation for myself. Chances are the docs will have the answer, along with a whole lot of other info which could really help you out. At least that is what I find!</p>
<p>So, next time you have a problem &#8211; look it up! Chances are you&#8217;ll get more than you asked for.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.red-library.com/why-you-should-read-documentation-34/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

