<?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: How to divide and conquer software projects effectively</title>
	<atom:link href="http://gojko.net/2009/10/19/how-to-divide-and-conquer-software-projects-effectively/feed/" rel="self" type="application/rss+xml" />
	<link>http://gojko.net/2009/10/19/how-to-divide-and-conquer-software-projects-effectively/</link>
	<description>Building software that matters</description>
	<lastBuildDate>Sat, 31 Jul 2010 09:50:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Steve Freeman</title>
		<link>http://gojko.net/2009/10/19/how-to-divide-and-conquer-software-projects-effectively/comment-page-1/#comment-63137</link>
		<dc:creator>Steve Freeman</dc:creator>
		<pubDate>Tue, 20 Oct 2009 12:51:55 +0000</pubDate>
		<guid isPermaLink="false">http://gojko.net/?p=1321#comment-63137</guid>
		<description>I think the nineties was about distributed computing, which later turned into Web Services. The big idea was about building up systems from collaborating subsystems through interface protocols.

I think the theme for the oughties, is the mash-up. 

As for Top-Down Decomposition, the trouble the first time around was the confusion and waste in the leaf nodes of the code. Now we have Refactoring, we can clean up as we go.</description>
		<content:encoded><![CDATA[<p>I think the nineties was about distributed computing, which later turned into Web Services. The big idea was about building up systems from collaborating subsystems through interface protocols.</p>
<p>I think the theme for the oughties, is the mash-up. </p>
<p>As for Top-Down Decomposition, the trouble the first time around was the confusion and waste in the leaf nodes of the code. Now we have Refactoring, we can clean up as we go.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Régis Desgroppes</title>
		<link>http://gojko.net/2009/10/19/how-to-divide-and-conquer-software-projects-effectively/comment-page-1/#comment-63069</link>
		<dc:creator>Régis Desgroppes</dc:creator>
		<pubDate>Mon, 19 Oct 2009 15:26:58 +0000</pubDate>
		<guid isPermaLink="false">http://gojko.net/?p=1321#comment-63069</guid>
		<description>A few words about a &quot;Divide and conquer&quot; debate: it&#039;s OK provided it doesn&#039;t lead to local optimizations giving no overall significant improvement or, worse, degrading global efficiency.
To some extend that could be compared to a purchase department succeeding in reducing costs by buying cheaper and/or larger stocks whereas the purchased goods are not of the required quality and/or in excess.
For more details:
- Implementing Lean Software Development by Tom &amp; Mary Poppendieck
- The Goal: A Process of Ongoing Improvement by Eliyahu M. Goldratt
Régis.</description>
		<content:encoded><![CDATA[<p>A few words about a &#8220;Divide and conquer&#8221; debate: it&#8217;s OK provided it doesn&#8217;t lead to local optimizations giving no overall significant improvement or, worse, degrading global efficiency.<br />
To some extend that could be compared to a purchase department succeeding in reducing costs by buying cheaper and/or larger stocks whereas the purchased goods are not of the required quality and/or in excess.<br />
For more details:<br />
- Implementing Lean Software Development by Tom &amp; Mary Poppendieck<br />
- The Goal: A Process of Ongoing Improvement by Eliyahu M. Goldratt<br />
Régis.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
