<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Design patterns and principles - Java Monkeys - tribe.net</title>
    <link>http://javamonkeys.tribe.net/thread/03dac3f0-25f1-4cc0-b3c8-8951c6934b4e?format=rss</link>
    <description>Tribe.net. Local Connections</description>
    <item>
      <title>Re: Design patterns and principles</title>
      <link>http://javamonkeys.tribe.net/thread/03dac3f0-25f1-4cc0-b3c8-8951c6934b4e#130ac540-b279-4bbf-afe4-e117b1ce32e7</link>
      <description>Totally agree. Its way more usefull to know what should not be done then knowing what 'should' be done.</description>
      <pubDate>Wed, 14 Feb 2007 21:22:47 GMT</pubDate>
      <guid isPermaLink="false">http://javamonkeys.tribe.net/thread/03dac3f0-25f1-4cc0-b3c8-8951c6934b4e#130ac540-b279-4bbf-afe4-e117b1ce32e7</guid>
      <dc:creator>Matthew</dc:creator>
      <dc:date>2007-02-14T21:22:47Z</dc:date>
    </item>
    <item>
      <title>Re: Design patterns and principles</title>
      <link>http://javamonkeys.tribe.net/thread/03dac3f0-25f1-4cc0-b3c8-8951c6934b4e#86474a39-32b9-4e1d-a79c-e7d02852dbe2</link>
      <description>Let me just add this, I am quite surprised with the backseat position anti-patterns get in general when it comes to Design patterns studies, as anti-patterns are a natural extension to Design patterns.  In other words, when reading about a particular Design pattern, there should be a section ready and handy on how one can abuse the pattern.  Anti-patterns are neglected because they are almost taught as a different subject, whereas it should be a natural fit with Design patterns literature.</description>
      <pubDate>Mon, 12 Feb 2007 12:43:42 GMT</pubDate>
      <guid isPermaLink="false">http://javamonkeys.tribe.net/thread/03dac3f0-25f1-4cc0-b3c8-8951c6934b4e#86474a39-32b9-4e1d-a79c-e7d02852dbe2</guid>
      <dc:creator>emblylan</dc:creator>
      <dc:date>2007-02-12T12:43:42Z</dc:date>
    </item>
    <item>
      <title>Re: Design patterns and principles</title>
      <link>http://javamonkeys.tribe.net/thread/03dac3f0-25f1-4cc0-b3c8-8951c6934b4e#0cfa8429-2867-45c1-aa0c-cafa616c3ec0</link>
      <description>I agree with you, but to the extent that every project (and more specifically the technologies used within the project) has its Best Practices, and Bad Practices (anti-patterns, lessons learned, case studies, call it what you will, lately it seems that the term Anti-Pattern is the in thing).&#xD;
&#xD;
I should have been more specific with my original question which was:  "...studies design patterns and principles?".  It should have been:  "...studies design patterns and principles for designing/architecting a software module from the ground up?".  By "module" I mean any piece of software that you write in isolation.  Now I know that any software one writes will never be in complete isolation, but I mean it in the sense that you are actually designing software completely from the ground up, where for the most part of your design it is as good as the rest of your design.  I hope this makes sense, please tell me to clarify more if not.&#xD;
&#xD;
I am aware of the anti-patterns in the scope of my work:  JBoss, EJB 2.1, Struts, Socket programming, etc.  For this I specifically am on the lookout for Anti-patterns (Lessons learned.)&#xD;
&#xD;
When designing software from the ground up, anti-patterns do not really play that much of a role for me, as each design principle automatically has a direct opposite, eg:&#xD;
 - Design your classes to have high cohesion (anti:  stay away from low cohesion)&#xD;
 - Design your classes to have loose coupling (anti:  tight coupling is not your friend)&#xD;
&#xD;
In summary:  I agree with anti-patterns, when you write software that depends more on frameworks/tools created by others, than on your own.  Design principles and patterns takes a priority for me when designing software from the ground up, which for the most part of it does not depend that much on frameworks/tools created by others.</description>
      <pubDate>Mon, 12 Feb 2007 07:43:54 GMT</pubDate>
      <guid isPermaLink="false">http://javamonkeys.tribe.net/thread/03dac3f0-25f1-4cc0-b3c8-8951c6934b4e#0cfa8429-2867-45c1-aa0c-cafa616c3ec0</guid>
      <dc:creator>emblylan</dc:creator>
      <dc:date>2007-02-12T07:43:54Z</dc:date>
    </item>
    <item>
      <title>Re: Design patterns and principles</title>
      <link>http://javamonkeys.tribe.net/thread/03dac3f0-25f1-4cc0-b3c8-8951c6934b4e#716a3007-5655-46be-b893-23a3d26adbf9</link>
      <description>Antipatterns depress me: I've lived through too many of them...</description>
      <pubDate>Sun, 11 Feb 2007 19:47:15 GMT</pubDate>
      <guid isPermaLink="false">http://javamonkeys.tribe.net/thread/03dac3f0-25f1-4cc0-b3c8-8951c6934b4e#716a3007-5655-46be-b893-23a3d26adbf9</guid>
      <dc:creator>Uncle Pauly</dc:creator>
      <dc:date>2007-02-11T19:47:15Z</dc:date>
    </item>
    <item>
      <title>Re: Design patterns and principles</title>
      <link>http://javamonkeys.tribe.net/thread/03dac3f0-25f1-4cc0-b3c8-8951c6934b4e#b69e39dd-d481-45ec-aa48-86f6cf2962b5</link>
      <description>Yeah, but I find that knowing antipatterns is more important to many projects.</description>
      <pubDate>Sun, 11 Feb 2007 19:26:17 GMT</pubDate>
      <guid isPermaLink="false">http://javamonkeys.tribe.net/thread/03dac3f0-25f1-4cc0-b3c8-8951c6934b4e#b69e39dd-d481-45ec-aa48-86f6cf2962b5</guid>
      <dc:creator>Matthew</dc:creator>
      <dc:date>2007-02-11T19:26:17Z</dc:date>
    </item>
    <item>
      <title>Re: Design patterns and principles</title>
      <link>http://javamonkeys.tribe.net/thread/03dac3f0-25f1-4cc0-b3c8-8951c6934b4e#b87b382c-8f93-4d8d-ad35-a9dbdbb1355e</link>
      <description>yes.</description>
      <pubDate>Thu, 08 Feb 2007 22:05:50 GMT</pubDate>
      <guid isPermaLink="false">http://javamonkeys.tribe.net/thread/03dac3f0-25f1-4cc0-b3c8-8951c6934b4e#b87b382c-8f93-4d8d-ad35-a9dbdbb1355e</guid>
      <dc:creator>Chris</dc:creator>
      <dc:date>2007-02-08T22:05:50Z</dc:date>
    </item>
    <item>
      <title>Design patterns and principles</title>
      <link>http://javamonkeys.tribe.net/thread/03dac3f0-25f1-4cc0-b3c8-8951c6934b4e#81276eac-7dcd-4522-be7a-26298e9b831b</link>
      <description>Any folks out there who studies design patterns and principles?&#xD;
&#xD;
Let me know, thanks.</description>
      <pubDate>Thu, 08 Feb 2007 18:32:35 GMT</pubDate>
      <guid isPermaLink="false">http://javamonkeys.tribe.net/thread/03dac3f0-25f1-4cc0-b3c8-8951c6934b4e#81276eac-7dcd-4522-be7a-26298e9b831b</guid>
      <dc:creator>emblylan</dc:creator>
      <dc:date>2007-02-08T18:32:35Z</dc:date>
    </item>
  </channel>
</rss>



