<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: The Pattern of Not Using Patterns - Part I</title>
	<link>http://www.retrospector.com/2006/05/16/the-pattern-of-not-using-patterns-part-i/</link>
	<description>A hindsight perspective on the everlasting trail of improvement.</description>
	<pubDate>Wed, 09 Jul 2008 03:37:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Terminus a Quo &#187; Blog Archive &#187; Infected With Patternitis</title>
		<link>http://www.retrospector.com/2006/05/16/the-pattern-of-not-using-patterns-part-i/#comment-8</link>
		<pubDate>Mon, 22 May 2006 15:24:14 +0000</pubDate>
		<guid>http://www.retrospector.com/2006/05/16/the-pattern-of-not-using-patterns-part-i/#comment-8</guid>
					<description>[...] Here is part one of a three-part article explaining why and when to use patterns in your software development project. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Here is part one of a three-part article explaining why and when to use patterns in your software development project. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: The Retrospector &#187; Blog Archive &#187; The Pattern of Not Using Patterns - Part III</title>
		<link>http://www.retrospector.com/2006/05/16/the-pattern-of-not-using-patterns-part-i/#comment-4</link>
		<pubDate>Mon, 22 May 2006 04:17:35 +0000</pubDate>
		<guid>http://www.retrospector.com/2006/05/16/the-pattern-of-not-using-patterns-part-i/#comment-4</guid>
					<description>[...] Not using patterns in software design and development leads to code that will probably work at first, but almost never withstands the test of time. This article is a continuation and conclusion of The Pattern of NOT Using Patterns – Part I &amp;#38; The Pattern of NOT Using Patterns – Part II which talked about how we get into situations where we don’t use patterns, when patterns can be appropriately applied to a project and what happens when they’re not applied when they should be. In this final segment, I intend to explain how differences in pattern familiarity can affect people as they’re working on a project. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Not using patterns in software design and development leads to code that will probably work at first, but almost never withstands the test of time. This article is a continuation and conclusion of The Pattern of NOT Using Patterns – Part I &#38; The Pattern of NOT Using Patterns – Part II which talked about how we get into situations where we don’t use patterns, when patterns can be appropriately applied to a project and what happens when they’re not applied when they should be. In this final segment, I intend to explain how differences in pattern familiarity can affect people as they’re working on a project. [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
