<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>MDBitz Development Resources &#187; Design Patterns</title>
	<atom:link href="http://resources.mdbitz.com/categories/design-patterns/feed/" rel="self" type="application/rss+xml" />
	<link>http://resources.mdbitz.com</link>
	<description></description>
	<lastBuildDate>Mon, 22 Nov 2010 14:25:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Don&#8217;t use Design Patterns just because you can, you Cargo Cult Programmer</title>
		<link>http://resources.mdbitz.com/2010/03/dont-use-design-patterns-just-because-you-can-you-cargo-cult-programmer/</link>
		<comments>http://resources.mdbitz.com/2010/03/dont-use-design-patterns-just-because-you-can-you-cargo-cult-programmer/#comments</comments>
		<pubDate>Wed, 10 Mar 2010 18:56:23 +0000</pubDate>
		<dc:creator>MDBitz - Matthew Denton</dc:creator>
				<category><![CDATA[Design Patterns]]></category>
		<category><![CDATA[Tips & Tricks]]></category>
		<category><![CDATA[Anti-Patterns]]></category>
		<category><![CDATA[Cargo Cult Programming]]></category>
		<category><![CDATA[Java]]></category>

		<guid isPermaLink="false">http://resources.mdbitz.com/?p=1133</guid>
		<description><![CDATA[Have you ever stumbled across a project and just think to yourself why does this class exist, or more specifically why did they use this design pattern? Recently I happened across one of those projects, in it the project used a Factory class that&#8217;s purpose was to instantiate and return a single class. In essence [...]]]></description>
		<wfw:commentRss>http://resources.mdbitz.com/2010/03/dont-use-design-patterns-just-because-you-can-you-cargo-cult-programmer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Constant Interface Antipattern &#8211; How not to define constants</title>
		<link>http://resources.mdbitz.com/2010/03/the-constant-interface-antipattern-how-not-to-define-constants/</link>
		<comments>http://resources.mdbitz.com/2010/03/the-constant-interface-antipattern-how-not-to-define-constants/#comments</comments>
		<pubDate>Thu, 04 Mar 2010 19:09:07 +0000</pubDate>
		<dc:creator>MDBitz - Matthew Denton</dc:creator>
				<category><![CDATA[Design Patterns]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Tips & Tricks]]></category>
		<category><![CDATA[Antipattern]]></category>
		<category><![CDATA[Constants]]></category>
		<category><![CDATA[import static]]></category>
		<category><![CDATA[Interface]]></category>

		<guid isPermaLink="false">http://resources.mdbitz.com/?p=1097</guid>
		<description><![CDATA[When working in applications that utilize a lot of variables I often come across interfaces containing nothing but constants. Instead of creating a class containing the constants the developers choose to define them in an interface that can be implemented by a class so that constants don&#8217;t need to be qualified to a class in [...]]]></description>
		<wfw:commentRss>http://resources.mdbitz.com/2010/03/the-constant-interface-antipattern-how-not-to-define-constants/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Factory Pattern and the Java Class Object</title>
		<link>http://resources.mdbitz.com/2009/09/factory-pattern-and-the-java-class-object/</link>
		<comments>http://resources.mdbitz.com/2009/09/factory-pattern-and-the-java-class-object/#comments</comments>
		<pubDate>Thu, 17 Sep 2009 16:16:25 +0000</pubDate>
		<dc:creator>MDBitz - Matthew Denton</dc:creator>
				<category><![CDATA[Design Patterns]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Class Object]]></category>
		<category><![CDATA[Factory Pattern]]></category>
		<category><![CDATA[Interfaces]]></category>

		<guid isPermaLink="false">http://resources.mdbitz.com/?p=224</guid>
		<description><![CDATA[Overview The Factory Pattern is a Software Design Pattern that is used to create an object without calling the specific object&#8217;s constructor.  This pattern allows a end user to call the factory to instantiate a class without having to know how to instantiate the class itself.  How it works is by the creation of a [...]]]></description>
		<wfw:commentRss>http://resources.mdbitz.com/2009/09/factory-pattern-and-the-java-class-object/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Anti-Pattern Fun</title>
		<link>http://resources.mdbitz.com/2009/08/anti-pattern-fun/</link>
		<comments>http://resources.mdbitz.com/2009/08/anti-pattern-fun/#comments</comments>
		<pubDate>Fri, 14 Aug 2009 15:49:40 +0000</pubDate>
		<dc:creator>mdbitz</dc:creator>
				<category><![CDATA[Design Patterns]]></category>
		<category><![CDATA[Anti-Patterns]]></category>

		<guid isPermaLink="false">http://mdbitz.com/resources/?p=78</guid>
		<description><![CDATA[Anti-Patterns are a pattern of behavior or design that proves to be counterproductive or inefficient to a project.  Although Anti-Patterns exist for Software and Object-Oriented designs my favorites mostly apply to organizational and project management (personal and group behaviors).]]></description>
		<wfw:commentRss>http://resources.mdbitz.com/2009/08/anti-pattern-fun/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Decorator : Design Pattern</title>
		<link>http://resources.mdbitz.com/2009/08/decorator-design-pattern/</link>
		<comments>http://resources.mdbitz.com/2009/08/decorator-design-pattern/#comments</comments>
		<pubDate>Fri, 14 Aug 2009 14:09:38 +0000</pubDate>
		<dc:creator>mdbitz</dc:creator>
				<category><![CDATA[Design Patterns]]></category>
		<category><![CDATA[Decorator]]></category>

		<guid isPermaLink="false">http://mdbitz.com/resources/?p=75</guid>
		<description><![CDATA[Overview Design Patterns are a reusable solutions to a commonly seen software desgin problem. The key item to remember is that these patterns are more like templates and instructions and are not reusable code. Although helpful and can solve many problems they are not usefull in every case and can hinder you from finding the [...]]]></description>
		<wfw:commentRss>http://resources.mdbitz.com/2009/08/decorator-design-pattern/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

