<?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: What is coupling, really?</title>
	<atom:link href="http://leansoftwareengineering.com/2007/08/08/what-is-coupling-really/feed/" rel="self" type="application/rss+xml" />
	<link>http://leansoftwareengineering.com/2007/08/08/what-is-coupling-really/</link>
	<description>Essays on the Continuous Delivery of High Quality Information Systems</description>
	<lastBuildDate>Wed, 01 Feb 2012 18:32:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Writing Elegant Code and the Maintainability Index. &#171; Light of Bytes</title>
		<link>http://leansoftwareengineering.com/2007/08/08/what-is-coupling-really/comment-page-1/#comment-9789</link>
		<dc:creator>Writing Elegant Code and the Maintainability Index. &#171; Light of Bytes</dc:creator>
		<pubDate>Sun, 05 Dec 2010 09:28:38 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/08/08/what-is-coupling-really/#comment-9789</guid>
		<description>[...] Coupling and Cohesion Index (Corey Ladas on Coupling) [...]</description>
		<content:encoded><![CDATA[<p>[...] Coupling and Cohesion Index (Corey Ladas on Coupling) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://leansoftwareengineering.com/2007/08/08/what-is-coupling-really/comment-page-1/#comment-4959</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 04 Mar 2009 19:41:43 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/08/08/what-is-coupling-really/#comment-4959</guid>
		<description>If only everyone bothered with good design.

I&#039;m currently working on a programming contract for a start-up company.  During the &#039;design meeting&#039;, the manager cut me and the other engineer short, when we were discussing the design, saying that &quot;We don&#039;t have time for this... we have a deadline to meet&quot;.

This guy is very well educated, but sadly not in software engineering!  This is his first software project (and probably last!).  I keep telling him how important it is to do things properly, and how much it costs if you don&#039;t do things properly.  However he just ignores me!

Shall I jump ship now!?</description>
		<content:encoded><![CDATA[<p>If only everyone bothered with good design.</p>
<p>I&#8217;m currently working on a programming contract for a start-up company.  During the &#8216;design meeting&#8217;, the manager cut me and the other engineer short, when we were discussing the design, saying that &#8220;We don&#8217;t have time for this&#8230; we have a deadline to meet&#8221;.</p>
<p>This guy is very well educated, but sadly not in software engineering!  This is his first software project (and probably last!).  I keep telling him how important it is to do things properly, and how much it costs if you don&#8217;t do things properly.  However he just ignores me!</p>
<p>Shall I jump ship now!?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Corey</title>
		<link>http://leansoftwareengineering.com/2007/08/08/what-is-coupling-really/comment-page-1/#comment-120</link>
		<dc:creator>Corey</dc:creator>
		<pubDate>Tue, 04 Sep 2007 19:40:03 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/08/08/what-is-coupling-really/#comment-120</guid>
		<description>Yes, wise people have said that the best designs are both bottom-up and top-down.

APIs are a good example because the balance between requirements and design is so apparent.  That balance is always present, but it makes itself most visible at the interfaces between systems (including users).  I hope to say more about why requirements definitions are so critical to quality, but rarely get the attention they deserve from the methodology community.
</description>
		<content:encoded><![CDATA[<p>Yes, wise people have said that the best designs are both bottom-up and top-down.</p>
<p>APIs are a good example because the balance between requirements and design is so apparent.  That balance is always present, but it makes itself most visible at the interfaces between systems (including users).  I hope to say more about why requirements definitions are so critical to quality, but rarely get the attention they deserve from the methodology community.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Campbell</title>
		<link>http://leansoftwareengineering.com/2007/08/08/what-is-coupling-really/comment-page-1/#comment-116</link>
		<dc:creator>Steve Campbell</dc:creator>
		<pubDate>Tue, 04 Sep 2007 19:16:59 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/08/08/what-is-coupling-really/#comment-116</guid>
		<description>Another way to look at this might be to note that practically, the system with the problem you describe has an API deficiency.  The user (developer) has to bring together too many parts in order to perform simple tasks.  

It is fairly common in a TDD system of any complexity, because the TDD process does not lend itself to a natural API evolution.  Nothing does really - APIs need to be designed intentionally in order to be good.</description>
		<content:encoded><![CDATA[<p>Another way to look at this might be to note that practically, the system with the problem you describe has an API deficiency.  The user (developer) has to bring together too many parts in order to perform simple tasks.  </p>
<p>It is fairly common in a TDD system of any complexity, because the TDD process does not lend itself to a natural API evolution.  Nothing does really &#8211; APIs need to be designed intentionally in order to be good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kanban systems for software development &#124; Lean Software Engineering</title>
		<link>http://leansoftwareengineering.com/2007/08/08/what-is-coupling-really/comment-page-1/#comment-101</link>
		<dc:creator>Kanban systems for software development &#124; Lean Software Engineering</dc:creator>
		<pubDate>Wed, 29 Aug 2007 21:41:54 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/08/08/what-is-coupling-really/#comment-101</guid>
		<description>[...] plan will occur according to the long-tailed probability distribution that you ought to have tattooed on your other eyeball. The fundamental strategy for managing uncertainty in any cause-and-effect process is the buffer. [...]</description>
		<content:encoded><![CDATA[<p>[...] plan will occur according to the long-tailed probability distribution that you ought to have tattooed on your other eyeball. The fundamental strategy for managing uncertainty in any cause-and-effect process is the buffer. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.385 seconds -->

