<?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: Kitchen Cupboard Anti-pattern</title>
	<link>http://blog.springsource.com/arjen/archives/2005/08/23/kitchen-cupboard-anti-pattern/</link>
	<description>A blog about programming in .NET and Java</description>
	<pubDate>Thu, 20 Nov 2008 11:38:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: American Coward</title>
		<link>http://blog.springsource.com/arjen/archives/2005/08/23/kitchen-cupboard-anti-pattern/#comment-267</link>
		<pubDate>Wed, 24 Aug 2005 07:51:41 +0000</pubDate>
		<guid>http://blog.springsource.com/arjen/archives/2005/08/23/kitchen-cupboard-anti-pattern/#comment-267</guid>
					<description>I'm not sure but this looks as valid to me. Chain of Responsibility and Bridge are also common patterns, ambiguous in definition.

Anyway, what is certain is that this is more of an antipattern than else. Just like GoldenHammer, or GuruDoesAll. And I like the name, it certainly is more sticky than the &quot;if it isn't broke, don't fix it&quot; principle.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure but this looks as valid to me. Chain of Responsibility and Bridge are also common patterns, ambiguous in definition.</p>
<p>Anyway, what is certain is that this is more of an antipattern than else. Just like GoldenHammer, or GuruDoesAll. And I like the name, it certainly is more sticky than the &#8220;if it isn&#8217;t broke, don&#8217;t fix it&#8221; principle.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Anonymous</title>
		<link>http://blog.springsource.com/arjen/archives/2005/08/23/kitchen-cupboard-anti-pattern/#comment-266</link>
		<pubDate>Tue, 23 Aug 2005 14:24:53 +0000</pubDate>
		<guid>http://blog.springsource.com/arjen/archives/2005/08/23/kitchen-cupboard-anti-pattern/#comment-266</guid>
					<description>I think patterns (and therefor anti-patterns) are supposed to describe something specific.  So when two people are talking, instead of describing a complex process, they can shortcut it by saying &quot;It implements the Command Pattern&quot;.  That way, you know the system generally behaves the way we all agree Command Pattern behaves.

The &quot;kitchen cupboard&quot; pattern can be just about anything at all (including just not being able to understand something that DOES work well).  

I'm not saying that what you are describing isn't valid, I just don't think it's really a pattern.</description>
		<content:encoded><![CDATA[<p>I think patterns (and therefor anti-patterns) are supposed to describe something specific.  So when two people are talking, instead of describing a complex process, they can shortcut it by saying &#8220;It implements the Command Pattern&#8221;.  That way, you know the system generally behaves the way we all agree Command Pattern behaves.</p>
<p>The &#8220;kitchen cupboard&#8221; pattern can be just about anything at all (including just not being able to understand something that DOES work well).  </p>
<p>I&#8217;m not saying that what you are describing isn&#8217;t valid, I just don&#8217;t think it&#8217;s really a pattern.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
