<?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: Developer Productivity in Highly Coupled Systems</title>
	<atom:link href="http://gorillajawn.com/wordpress/2009/01/12/developer-productivity-in-highly-coupled-systems/feed/" rel="self" type="application/rss+xml" />
	<link>http://gorillajawn.com/wordpress/2009/01/12/developer-productivity-in-highly-coupled-systems/</link>
	<description>Enterprise Software Consultant</description>
	<lastBuildDate>Mon, 15 Mar 2010 20:02:48 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Stu Stern</title>
		<link>http://gorillajawn.com/wordpress/2009/01/12/developer-productivity-in-highly-coupled-systems/comment-page-1/#comment-20663</link>
		<dc:creator>Stu Stern</dc:creator>
		<pubDate>Tue, 13 Jan 2009 23:26:39 +0000</pubDate>
		<guid isPermaLink="false">http://ectropic.com/wordpress/?p=159#comment-20663</guid>
		<description>There are many factors driving functional decomposition of a system. Developers tend to &quot;over-decouple&quot; when attempting to accomodate for &quot;possible change&quot;. (And how often do such changes really wind up hiding behind a pre-exiting facade rather than requiring some larger code refactoring anyway?).

I agree with you that an even bigger driver of decoupling than such evolutionary considerations is the need to break up a system so that it can be built by multiple people or teams working in tandem.

Too many architects overlook such &quot;buildability&quot; considerations when devising an architecture, but they&#039;re cross-cutting concerns that need to be considered along with all the more commonly discussed concerns (scalability, availability, etc) that drive the definition of a system architecture.</description>
		<content:encoded><![CDATA[<p>There are many factors driving functional decomposition of a system. Developers tend to &#8220;over-decouple&#8221; when attempting to accomodate for &#8220;possible change&#8221;. (And how often do such changes really wind up hiding behind a pre-exiting facade rather than requiring some larger code refactoring anyway?).</p>
<p>I agree with you that an even bigger driver of decoupling than such evolutionary considerations is the need to break up a system so that it can be built by multiple people or teams working in tandem.</p>
<p>Too many architects overlook such &#8220;buildability&#8221; considerations when devising an architecture, but they&#8217;re cross-cutting concerns that need to be considered along with all the more commonly discussed concerns (scalability, availability, etc) that drive the definition of a system architecture.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
