<?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: Dangers of Design Patterns</title>
	<atom:link href="http://blog.markwshead.com/95/dangers-of-design-patterns/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.markwshead.com/95/dangers-of-design-patterns/</link>
	<description>Mark's thoughts on being Mark Shead and other random subjects</description>
	<lastBuildDate>Thu, 29 Jul 2010 03:22:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Kumar Chetan Sharma</title>
		<link>http://blog.markwshead.com/95/dangers-of-design-patterns/comment-page-1/#comment-9</link>
		<dc:creator>Kumar Chetan Sharma</dc:creator>
		<pubDate>Wed, 07 Jan 2009 09:43:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.markwshead.com/archives/2005/07/23/dangers-of-design-patterns.html#comment-9</guid>
		<description>I have only found few of the patterns useful in my career of web application development. But usually these patterns introduce complexity and extra bytes of codes which matter a lot when I write and application. I wrote a custom CMS for less than 200KB of code. The client is happy. They can scale it, enhance it and do whatever they wish to do. The template or &quot;view&quot; is totally separate from model and/or controllers and it takes same amount of simplicity to create a view for this CMS as it will take for any other. But this CMS is not based on MVC. The only pattern if I did use was singleton which IMHO I could have simply avoided. My point is Design Patterns are not silver bullets.</description>
		<content:encoded><![CDATA[<p>I have only found few of the patterns useful in my career of web application development. But usually these patterns introduce complexity and extra bytes of codes which matter a lot when I write and application. I wrote a custom CMS for less than 200KB of code. The client is happy. They can scale it, enhance it and do whatever they wish to do. The template or &#8220;view&#8221; is totally separate from model and/or controllers and it takes same amount of simplicity to create a view for this CMS as it will take for any other. But this CMS is not based on MVC. The only pattern if I did use was singleton which IMHO I could have simply avoided. My point is Design Patterns are not silver bullets.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
