<?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: From Monkey to Man &#8211; Part I</title>
	<atom:link href="http://www.bagonca.com/blog/2009/06/24/design-patterns-from-monkey-to-man-part-i/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bagonca.com/blog/2009/06/24/design-patterns-from-monkey-to-man-part-i/</link>
	<description>Yet another developer blog</description>
	<lastBuildDate>Mon, 19 Dec 2011 21:48:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Ram Sundararajan</title>
		<link>http://www.bagonca.com/blog/2009/06/24/design-patterns-from-monkey-to-man-part-i/comment-page-1/#comment-169</link>
		<dc:creator>Ram Sundararajan</dc:creator>
		<pubDate>Wed, 29 Jul 2009 09:04:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.bagonca.com/blog/?p=555#comment-169</guid>
		<description>I just updated the post with 4 others :-)</description>
		<content:encoded><![CDATA[<p>I just updated the post with 4 others :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PEZ</title>
		<link>http://www.bagonca.com/blog/2009/06/24/design-patterns-from-monkey-to-man-part-i/comment-page-1/#comment-150</link>
		<dc:creator>PEZ</dc:creator>
		<pubDate>Sat, 27 Jun 2009 09:15:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.bagonca.com/blog/?p=555#comment-150</guid>
		<description>I doubt it. I think we&#039;ll get creativity at a higher level.</description>
		<content:encoded><![CDATA[<p>I doubt it. I think we&#8217;ll get creativity at a higher level.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mel</title>
		<link>http://www.bagonca.com/blog/2009/06/24/design-patterns-from-monkey-to-man-part-i/comment-page-1/#comment-149</link>
		<dc:creator>Mel</dc:creator>
		<pubDate>Fri, 26 Jun 2009 16:39:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.bagonca.com/blog/?p=555#comment-149</guid>
		<description>I can recommend the book Head First Design Patterns: 
http://oreilly.com/catalog/9780596007126/

The whole Head First series takes a slightly different approach in their books  with a lot of pictures, interesting and easy to grasp examples. 

For me this worked really well and I found &quot;Head First Design Patterns&quot; a good introduction into the some of the more known design patterns.I think were the original GoF book can get a little bit dry, this book is really fun to read. 

Agree with Ram. It&#039;s good to know which techniques are out there and what other programmers are using in their daily work.</description>
		<content:encoded><![CDATA[<p>I can recommend the book Head First Design Patterns:<br />
<a href="http://oreilly.com/catalog/9780596007126/" rel="nofollow">http://oreilly.com/catalog/9780596007126/</a></p>
<p>The whole Head First series takes a slightly different approach in their books  with a lot of pictures, interesting and easy to grasp examples. </p>
<p>For me this worked really well and I found &#8220;Head First Design Patterns&#8221; a good introduction into the some of the more known design patterns.I think were the original GoF book can get a little bit dry, this book is really fun to read. </p>
<p>Agree with Ram. It&#8217;s good to know which techniques are out there and what other programmers are using in their daily work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Priya</title>
		<link>http://www.bagonca.com/blog/2009/06/24/design-patterns-from-monkey-to-man-part-i/comment-page-1/#comment-147</link>
		<dc:creator>Priya</dc:creator>
		<pubDate>Thu, 25 Jun 2009 09:56:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.bagonca.com/blog/?p=555#comment-147</guid>
		<description>Good initiative, Ram! 
Copying in a nicer and better way! But I guess as time goes, creativity will vanish if reusable techniques are utilized again and again.</description>
		<content:encoded><![CDATA[<p>Good initiative, Ram!<br />
Copying in a nicer and better way! But I guess as time goes, creativity will vanish if reusable techniques are utilized again and again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RamESH</title>
		<link>http://www.bagonca.com/blog/2009/06/24/design-patterns-from-monkey-to-man-part-i/comment-page-1/#comment-146</link>
		<dc:creator>RamESH</dc:creator>
		<pubDate>Thu, 25 Jun 2009 04:36:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.bagonca.com/blog/?p=555#comment-146</guid>
		<description>I feel that for implementing design patterns we need to start thinking &quot;design&quot; when we code...we got to get the general flow of the code. For this some knowledge of the available patterns in the market will be very helpful. That was the intent of the article rather than evagelising C++ instead of Python :-) 

I feel that we can get a lot of inspiration from this book, eventhough it was written very many years back.

Yeah I have seen the Google video. You know sometimes I feel that we should buy Google ;-) They are pro Python and use it quite a bi themselves..Its so nice to look at their code and tech. discussions.</description>
		<content:encoded><![CDATA[<p>I feel that for implementing design patterns we need to start thinking &#8220;design&#8221; when we code&#8230;we got to get the general flow of the code. For this some knowledge of the available patterns in the market will be very helpful. That was the intent of the article rather than evagelising C++ instead of Python :-) </p>
<p>I feel that we can get a lot of inspiration from this book, eventhough it was written very many years back.</p>
<p>Yeah I have seen the Google video. You know sometimes I feel that we should buy Google ;-) They are pro Python and use it quite a bi themselves..Its so nice to look at their code and tech. discussions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Walter</title>
		<link>http://www.bagonca.com/blog/2009/06/24/design-patterns-from-monkey-to-man-part-i/comment-page-1/#comment-145</link>
		<dc:creator>Walter</dc:creator>
		<pubDate>Wed, 24 Jun 2009 14:33:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.bagonca.com/blog/?p=555#comment-145</guid>
		<description>Gang of Four? So first they made music, and then wrote a book about software design? Cool.</description>
		<content:encoded><![CDATA[<p>Gang of Four? So first they made music, and then wrote a book about software design? Cool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PEZ</title>
		<link>http://www.bagonca.com/blog/2009/06/24/design-patterns-from-monkey-to-man-part-i/comment-page-1/#comment-144</link>
		<dc:creator>PEZ</dc:creator>
		<pubDate>Wed, 24 Jun 2009 14:04:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.bagonca.com/blog/?p=555#comment-144</guid>
		<description>I see. Then I&#039;ll relax again. =) I think it&#039;s important to remember that each language has it&#039;s Tao. Design Patterns vary a lot between languages. Therefore that book can mainly serve as a manifest for the design patterns movement (as long as we&#039;re not implementing in C++). We probably should be looking for good resources for Python Design Patterns. Google to the rescue, I found these immediately:

Part 1: http://video.google.com/videoplay?docid=-3035093035748181693
Part 2: http://video.google.com/videoplay?docid=-3246451475733984168 (Starts off with a discussion about paging)

Actually I&#039;ve found those before. Have them on my iPod. They&#039;re excellent.

I don&#039;t think we need to build a platform to enable patterns. We just need to start using them. We are using them already here and there. But to leverage for real we should use them more explicitly and and of course also put a tag in the doc strings which pattern is in use.</description>
		<content:encoded><![CDATA[<p>I see. Then I&#8217;ll relax again. =) I think it&#8217;s important to remember that each language has it&#8217;s Tao. Design Patterns vary a lot between languages. Therefore that book can mainly serve as a manifest for the design patterns movement (as long as we&#8217;re not implementing in C++). We probably should be looking for good resources for Python Design Patterns. Google to the rescue, I found these immediately:</p>
<p>Part 1: <a href="http://video.google.com/videoplay?docid=-3035093035748181693" rel="nofollow">http://video.google.com/videoplay?docid=-3035093035748181693</a><br />
Part 2: <a href="http://video.google.com/videoplay?docid=-3246451475733984168" rel="nofollow">http://video.google.com/videoplay?docid=-3246451475733984168</a> (Starts off with a discussion about paging)</p>
<p>Actually I&#8217;ve found those before. Have them on my iPod. They&#8217;re excellent.</p>
<p>I don&#8217;t think we need to build a platform to enable patterns. We just need to start using them. We are using them already here and there. But to leverage for real we should use them more explicitly and and of course also put a tag in the doc strings which pattern is in use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ram Sundararajan</title>
		<link>http://www.bagonca.com/blog/2009/06/24/design-patterns-from-monkey-to-man-part-i/comment-page-1/#comment-143</link>
		<dc:creator>Ram Sundararajan</dc:creator>
		<pubDate>Wed, 24 Jun 2009 13:53:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.bagonca.com/blog/?p=555#comment-143</guid>
		<description>Yepp, there are four people who wrote the book :-)

What I mean with taking time is that we do not yet have a design pattern approach for many things.  So I believe that it will take more time for us to build the platform and enable patterns in the code.

It was not a technical issue with Python. Python has great support for any good design pattern. It was more of an implementation set back.

Its easier and faster to hack around the code and create technical debt rather than creating good designs.</description>
		<content:encoded><![CDATA[<p>Yepp, there are four people who wrote the book :-)</p>
<p>What I mean with taking time is that we do not yet have a design pattern approach for many things.  So I believe that it will take more time for us to build the platform and enable patterns in the code.</p>
<p>It was not a technical issue with Python. Python has great support for any good design pattern. It was more of an implementation set back.</p>
<p>Its easier and faster to hack around the code and create technical debt rather than creating good designs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PEZ</title>
		<link>http://www.bagonca.com/blog/2009/06/24/design-patterns-from-monkey-to-man-part-i/comment-page-1/#comment-142</link>
		<dc:creator>PEZ</dc:creator>
		<pubDate>Wed, 24 Jun 2009 13:45:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.bagonca.com/blog/?p=555#comment-142</guid>
		<description>That book is written by the Eric Gamma plus some more poeople, if I remember correctly. The Gang of Four. Just noting. =)

I don&#039;t think I understand this part: &quot;It can be implemented in Python although it might take a little more work than an ad hoc solution.&quot;</description>
		<content:encoded><![CDATA[<p>That book is written by the Eric Gamma plus some more poeople, if I remember correctly. The Gang of Four. Just noting. =)</p>
<p>I don&#8217;t think I understand this part: &#8220;It can be implemented in Python although it might take a little more work than an ad hoc solution.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ram Sundararajan</title>
		<link>http://www.bagonca.com/blog/2009/06/24/design-patterns-from-monkey-to-man-part-i/comment-page-1/#comment-141</link>
		<dc:creator>Ram Sundararajan</dc:creator>
		<pubDate>Wed, 24 Jun 2009 13:41:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.bagonca.com/blog/?p=555#comment-141</guid>
		<description>Yeah Barry, crush or get crushed ;-)</description>
		<content:encoded><![CDATA[<p>Yeah Barry, crush or get crushed ;-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

