<?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: Design patterns</title>
	<atom:link href="http://bencrowder.net/blog/2006/05/design-patterns/feed/" rel="self" type="application/rss+xml" />
	<link>http://bencrowder.net/blog/2006/05/design-patterns/</link>
	<description>I make stuff.</description>
	<lastBuildDate>Sat, 13 Mar 2010 21:35:21 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Beyond &#187; Blog Archive &#187; Login and design patterns</title>
		<link>http://bencrowder.net/blog/2006/05/design-patterns/#comment-120</link>
		<dc:creator>Beyond &#187; Blog Archive &#187; Login and design patterns</dc:creator>
		<pubDate>Wed, 24 May 2006 23:58:55 +0000</pubDate>
		<guid isPermaLink="false">http://outsidethebox.blankslate.net/2006/05/24/design-patterns/#comment-120</guid>
		<description>[...] Incidentally, I&#8217;m now reading through some design pattern libraries, and the stuff I&#8217;m finding is important enough that I&#8217;ll try to read through most of it before continuing with the interface design. Why? Because they give rationales for each design pattern (when and where to use it, when not to, things to be aware of, etc.), which are very, very helpful. And I have a strong suspicion that designing the main interface will be a lot easier after having read through them. We&#8217;ll see. I really, really, really like the idea of design patterns, by the way. If only I&#8217;d come across this stuff a few years ago&#8230;   Technorati Tags: design patterns [...]</description>
		<content:encoded><![CDATA[<p>[...] Incidentally, I&#8217;m now reading through some design pattern libraries, and the stuff I&#8217;m finding is important enough that I&#8217;ll try to read through most of it before continuing with the interface design. Why? Because they give rationales for each design pattern (when and where to use it, when not to, things to be aware of, etc.), which are very, very helpful. And I have a strong suspicion that designing the main interface will be a lot easier after having read through them. We&#8217;ll see. I really, really, really like the idea of design patterns, by the way. If only I&#8217;d come across this stuff a few years ago&#8230;   Technorati Tags: design patterns [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
