tag:blogger.com,1999:blog-26282638.post5125107169329461570..comments2018-02-28T21:37:39.528-06:00Comments on Apurv Kumaria's Haven: Present ProjectApurv Kumariahttp://www.blogger.com/profile/15400213610986021544noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-26282638.post-62241877121620025222008-02-17T12:52:00.000-06:002008-02-17T12:52:00.000-06:00I think thats what I was told when I talked to peo...I think thats what I was told when I talked to people at ThoughtWorks. It is simply a tool for writing clean code and self documenting, one of the part of Agile practices. <BR/>It is supposed to be a way to give importance to the fact of the open-close principle. <BR/>In Ruby, the problem of some design patterns is solved because Ruby has open classes.<BR/>I will be getting more involved with the remaining 5 weeks out of 6 weeks here in Bangalore and will be able to understand it better after that, though thanks a lot for your comment and the book!Apurv Kumariahttps://www.blogger.com/profile/15400213610986021544noreply@blogger.comtag:blogger.com,1999:blog-26282638.post-19800709221212434372008-02-17T07:03:00.000-06:002008-02-17T07:03:00.000-06:00The most interesting explanation of design pattern...The most interesting explanation of design patterns I've heard so far is that they're very useful if used as a communicational tool i.e. members of the team can intuitively understand how a bit of code works just from the design pattern being used. I've not yet seen design patterns being put in just for the sake of it - but maybe I'm not watching close enough!<BR/><BR/>This book is supposed to be pretty good with regards to introducing patterns into your code:<BR/><BR/>http://www.amazon.co.uk/Refactoring-Patterns-Addison-Wesley-Signature-Kerievsky/dp/0321213351/ref=sr_1_1?ie=UTF8&s=books&qid=1203253329&sr=8-1Mark Needhamhttps://www.blogger.com/profile/10917383515164513079noreply@blogger.com