<?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: Agile Development Teams Follow This Simple Principle</title>
	<atom:link href="http://brainslink.com/2012/06/agile-development-teams-follow-this-simple-principle/feed/" rel="self" type="application/rss+xml" />
	<link>http://brainslink.com/2012/06/agile-development-teams-follow-this-simple-principle/</link>
	<description></description>
	<lastBuildDate>Mon, 17 Jun 2013 10:26:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Vin</title>
		<link>http://brainslink.com/2012/06/agile-development-teams-follow-this-simple-principle/comment-page-1/#comment-555</link>
		<dc:creator>Vin</dc:creator>
		<pubDate>Mon, 11 Jun 2012 23:40:14 +0000</pubDate>
		<guid isPermaLink="false">http://brainslink.com/?p=1655#comment-555</guid>
		<description><![CDATA[Jordan, while we may disagree on some of the finer points, it&#039;s clear that we have general agreement. Simpler is better. Don&#039;t add complexity without justification.]]></description>
		<content:encoded><![CDATA[<p>Jordan, while we may disagree on some of the finer points, it&#8217;s clear that we have general agreement. Simpler is better. Don&#8217;t add complexity without justification.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jordan</title>
		<link>http://brainslink.com/2012/06/agile-development-teams-follow-this-simple-principle/comment-page-1/#comment-554</link>
		<dc:creator>Jordan</dc:creator>
		<pubDate>Mon, 11 Jun 2012 04:59:54 +0000</pubDate>
		<guid isPermaLink="false">http://brainslink.com/?p=1655#comment-554</guid>
		<description><![CDATA[Hi Vin

 Interesting post..... I had a small quibble about the Occam part and then get to the more meaty aspects I guess.

 Occam&#039;s Razor is explaining unknown phenomenon using the simplest theory; that&#039;s different than engineering the simplest system possible (the KISS/YAGNI principle).

 Your last sentence says &quot;Add complexity...only if needed&quot;.

 I would disagree here.

 The Turing Complex theorem states that any more complex program running on some more complex hardware could be written in a simpler language using a simpler machine, but it would take more time to write and run.

 So there is never a &quot;need&quot; -- per se --  to do the more complex thing -- there is just the desire/business case to do so.

 There is never a &quot;need&quot; to use separate name spaces, to split up the project, to use a more advanced language, to use a SQL database, all those things *could* be done using a simpler system. 

 At what point is the simpler system no longer the best solution? That is a judgement call, in some ways, and a business analysis decision on the other hand.

 I think people should use the more complex method &quot;when it makes sense&quot; -- not just &quot;only if needed&quot;.

 Judgement is a large part of the sw dev game, and a big reason why experienced developers bring more to the table.

 Best regards,
Jordan]]></description>
		<content:encoded><![CDATA[<p>Hi Vin</p>
<p> Interesting post&#8230;.. I had a small quibble about the Occam part and then get to the more meaty aspects I guess.</p>
<p> Occam&#8217;s Razor is explaining unknown phenomenon using the simplest theory; that&#8217;s different than engineering the simplest system possible (the KISS/YAGNI principle).</p>
<p> Your last sentence says &#8220;Add complexity&#8230;only if needed&#8221;.</p>
<p> I would disagree here.</p>
<p> The Turing Complex theorem states that any more complex program running on some more complex hardware could be written in a simpler language using a simpler machine, but it would take more time to write and run.</p>
<p> So there is never a &#8220;need&#8221; &#8212; per se &#8212;  to do the more complex thing &#8212; there is just the desire/business case to do so.</p>
<p> There is never a &#8220;need&#8221; to use separate name spaces, to split up the project, to use a more advanced language, to use a SQL database, all those things *could* be done using a simpler system. </p>
<p> At what point is the simpler system no longer the best solution? That is a judgement call, in some ways, and a business analysis decision on the other hand.</p>
<p> I think people should use the more complex method &#8220;when it makes sense&#8221; &#8212; not just &#8220;only if needed&#8221;.</p>
<p> Judgement is a large part of the sw dev game, and a big reason why experienced developers bring more to the table.</p>
<p> Best regards,<br />
Jordan</p>
]]></content:encoded>
	</item>
</channel>
</rss>
