<?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 III</title>
	<link>http://www.retrospector.com/2006/05/19/the-pattern-of-not-using-patterns-part-iii/</link>
	<description>A hindsight perspective on the everlasting trail of improvement.</description>
	<pubDate>Tue, 07 Oct 2008 02:47:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Retrospector</title>
		<link>http://www.retrospector.com/2006/05/19/the-pattern-of-not-using-patterns-part-iii/#comment-10</link>
		<pubDate>Mon, 22 May 2006 22:37:41 +0000</pubDate>
		<guid>http://www.retrospector.com/2006/05/19/the-pattern-of-not-using-patterns-part-iii/#comment-10</guid>
					<description>I really like this analogy.  I think it applies very well with regards to those that really know the patterns well.  Some people know the fundamentals behind the patterns without knowing the formalized names or standardized implementations.  Patterns are derived from people's trial &amp; error experience with development.  One day a recurrence caught someone's eye and they probably used it again.  I would agree that once you get to the point where you're using patterns (either pre-defined or not) w/o thinking about them there's no need to formally plan or define them into the project plan.  Thanks for the comment.</description>
		<content:encoded><![CDATA[<p>I really like this analogy.  I think it applies very well with regards to those that really know the patterns well.  Some people know the fundamentals behind the patterns without knowing the formalized names or standardized implementations.  Patterns are derived from people&#8217;s trial &#038; error experience with development.  One day a recurrence caught someone&#8217;s eye and they probably used it again.  I would agree that once you get to the point where you&#8217;re using patterns (either pre-defined or not) w/o thinking about them there&#8217;s no need to formally plan or define them into the project plan.  Thanks for the comment.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Guy Incognito</title>
		<link>http://www.retrospector.com/2006/05/19/the-pattern-of-not-using-patterns-part-iii/#comment-7</link>
		<pubDate>Mon, 22 May 2006 15:03:21 +0000</pubDate>
		<guid>http://www.retrospector.com/2006/05/19/the-pattern-of-not-using-patterns-part-iii/#comment-7</guid>
					<description>I feel like people see patterns wrong. In my mind, it is like music theory: It isn't so much rules to follow as it is a way of describing order that things tend to find themselves in. In any non-trivial piece of software (well, OO software) I usually end up using a pattern or three whether I think about it or not. It's just better to know that it is there so you can apply your general knowledge of that pattern to making that particular piece of software come out better.</description>
		<content:encoded><![CDATA[<p>I feel like people see patterns wrong. In my mind, it is like music theory: It isn&#8217;t so much rules to follow as it is a way of describing order that things tend to find themselves in. In any non-trivial piece of software (well, OO software) I usually end up using a pattern or three whether I think about it or not. It&#8217;s just better to know that it is there so you can apply your general knowledge of that pattern to making that particular piece of software come out better.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
