<?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: Coupling Is Your Friend</title>
	<atom:link href="http://lostechies.com/derickbailey/2010/04/12/coupling-is-your-friend/feed/" rel="self" type="application/rss+xml" />
	<link>http://lostechies.com/derickbailey/2010/04/12/coupling-is-your-friend/</link>
	<description>Better Than Yesterday</description>
	<lastBuildDate>Fri, 24 May 2013 06:39:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: John Sonmez</title>
		<link>http://lostechies.com/derickbailey/2010/04/12/coupling-is-your-friend/#comment-777</link>
		<dc:creator>John Sonmez</dc:creator>
		<pubDate>Tue, 13 Apr 2010 14:21:29 +0000</pubDate>
		<guid isPermaLink="false">/blogs/derickbailey/archive/2010/04/12/coupling-is-your-friend.aspx#comment-777</guid>
		<description>Good post.  I think this is a size of the lego blocks problem.
I have found with coupling, what we are really trying to achieve is to determine the correct size of the lego blocks we are creating.  

Creating things that are too loosely coupled is akin to creating very small lego blocks, and lots of them.  While this isolates change, it can also make it very difficult to build anything.

Creating things that are too highly coupled is akin to creating 1 or two huge lego blocks.  Also not very useful for building anything, and is highly susceptible to any changes.

Getting the right size of the blocks seems to be the key.  I have also found that certain parts of the application, should have different size blocks, if that makes sense.

You make a good point that not too many are aware of when they toss around words like loose coupling, but highly cohesive.</description>
		<content:encoded><![CDATA[<p>Good post.  I think this is a size of the lego blocks problem.<br />
I have found with coupling, what we are really trying to achieve is to determine the correct size of the lego blocks we are creating.  </p>
<p>Creating things that are too loosely coupled is akin to creating very small lego blocks, and lots of them.  While this isolates change, it can also make it very difficult to build anything.</p>
<p>Creating things that are too highly coupled is akin to creating 1 or two huge lego blocks.  Also not very useful for building anything, and is highly susceptible to any changes.</p>
<p>Getting the right size of the blocks seems to be the key.  I have also found that certain parts of the application, should have different size blocks, if that makes sense.</p>
<p>You make a good point that not too many are aware of when they toss around words like loose coupling, but highly cohesive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chadmyers</title>
		<link>http://lostechies.com/derickbailey/2010/04/12/coupling-is-your-friend/#comment-776</link>
		<dc:creator>chadmyers</dc:creator>
		<pubDate>Mon, 12 Apr 2010 23:58:55 +0000</pubDate>
		<guid isPermaLink="false">/blogs/derickbailey/archive/2010/04/12/coupling-is-your-friend.aspx#comment-776</guid>
		<description>Loosely coupled, highly cohesive should be the goal.  Not entirely decoupled, but coupled to the right things for the right reasons in the right places where it makes the most sense :)

See, it&#039;s just that easy :)</description>
		<content:encoded><![CDATA[<p>Loosely coupled, highly cohesive should be the goal.  Not entirely decoupled, but coupled to the right things for the right reasons in the right places where it makes the most sense :)</p>
<p>See, it&#8217;s just that easy :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
