 <?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"
	>
<channel>
	<title>Comments on: Detail versus Perspective</title>
	<atom:link href="http://blog.wioota.com/2006/09/27/detail-versus-perspective/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.wioota.com/2006/09/27/detail-versus-perspective/</link>
	<description>I have nothing to say and I say it.</description>
	<pubDate>Thu, 04 Dec 2008 18:58:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: wioota.com &#187; Blog Archive &#187; Evangelizing Quality</title>
		<link>http://blog.wioota.com/2006/09/27/detail-versus-perspective/#comment-24</link>
		<dc:creator>wioota.com &#187; Blog Archive &#187; Evangelizing Quality</dc:creator>
		<pubDate>Sat, 14 Oct 2006 07:06:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wioota.com/2006/09/27/detail-versus-perspective/#comment-24</guid>
		<description>[...] In my post detail versus perspective I had discussed the trap of fiddling with details whilst the truly valuable contribution to the success of your organisation languished. This is not in conflict with achieving quality in your work as often quality (attention to detail, usability, accessibility, reusability, literate code - whatever it is that provides ongoing benefit inside and out of your ogranisation) is that truly valuable contribution. [...]</description>
		<content:encoded><![CDATA[<p>[...] In my post detail versus perspective I had discussed the trap of fiddling with details whilst the truly valuable contribution to the success of your organisation languished. This is not in conflict with achieving quality in your work as often quality (attention to detail, usability, accessibility, reusability, literate code - whatever it is that provides ongoing benefit inside and out of your ogranisation) is that truly valuable contribution. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
