<?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"
	>
<channel>
	<title>Comments on: Joe&#8217;s ten rules of commercial software development</title>
	<atom:link href="http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/</link>
	<description>Ace King, Check it Out!</description>
	<pubDate>Thu, 20 Nov 2008 13:39:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Ozgen</title>
		<link>http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-10520</link>
		<dc:creator>Ozgen</dc:creator>
		<pubDate>Tue, 19 Dec 2006 21:06:28 +0000</pubDate>
		<guid isPermaLink="false">http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-10520</guid>
		<description>#8 is wisdom applied to development! Target dates keep on slipping when certain features refuse to cooperate, or simply don't do what they are supposed to. In other words, rule #8 boils down to applying rule #9 to those asshole features :-)</description>
		<content:encoded><![CDATA[<p>#8 is wisdom applied to development! Target dates keep on slipping when certain features refuse to cooperate, or simply don&#8217;t do what they are supposed to. In other words, rule #8 boils down to applying rule #9 to those asshole features <img src='http://joedrumgoole.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Toby</title>
		<link>http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-8872</link>
		<dc:creator>Toby</dc:creator>
		<pubDate>Fri, 08 Dec 2006 06:37:18 +0000</pubDate>
		<guid isPermaLink="false">http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-8872</guid>
		<description>Context, Context, CONTEXT.  All of these things are true... sometimes.  Maybe even most of the time, but if you don't remember to take things in context you're sol anyway</description>
		<content:encoded><![CDATA[<p>Context, Context, CONTEXT.  All of these things are true&#8230; sometimes.  Maybe even most of the time, but if you don&#8217;t remember to take things in context you&#8217;re sol anyway</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Len McGrane</title>
		<link>http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-8850</link>
		<dc:creator>Len McGrane</dc:creator>
		<pubDate>Fri, 08 Dec 2006 01:23:35 +0000</pubDate>
		<guid isPermaLink="false">http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-8850</guid>
		<description>You said it, Joe. If someone can't work in a team ... remove them! This is something &lt;a href="http://www.teamworx.cc" rel="nofollow"&gt;corporate team building programs&lt;/a&gt; &lt;b&gt;DON'T&lt;/b&gt; teach. They encourage a team to "build" and work together. But, even though labor laws and regulations make it difficult to dismiss staff, it will be the best thing you can do with a disruptive team member. Actually, for this reason, I have started to work with &lt;a href="http://www.ithands.com" rel="nofollow"&gt;developers in India&lt;/a&gt;. So far it has worked out fine. But if their teams, or individuals, don't work well for me I can easily slip away to someone else.</description>
		<content:encoded><![CDATA[<p>You said it, Joe. If someone can&#8217;t work in a team &#8230; remove them! This is something <a href="http://www.teamworx.cc" rel="nofollow">corporate team building programs</a> <b>DON&#8217;T</b> teach. They encourage a team to &#8220;build&#8221; and work together. But, even though labor laws and regulations make it difficult to dismiss staff, it will be the best thing you can do with a disruptive team member. Actually, for this reason, I have started to work with <a href="http://www.ithands.com" rel="nofollow">developers in India</a>. So far it has worked out fine. But if their teams, or individuals, don&#8217;t work well for me I can easily slip away to someone else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Copacetic &#187; Blog Archive &#187; Somebody else believes in firing the asshole</title>
		<link>http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-6212</link>
		<dc:creator>Copacetic &#187; Blog Archive &#187; Somebody else believes in firing the asshole</dc:creator>
		<pubDate>Thu, 02 Nov 2006 13:42:27 +0000</pubDate>
		<guid isPermaLink="false">http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-6212</guid>
		<description>[...] Dontcha just love external validation. Robert Sutton also believes in firing the Asshole&#160;(see rule 9). [...]</description>
		<content:encoded><![CDATA[<p>[...] Dontcha just love external validation. Robert Sutton also believes in firing the Asshole&nbsp;(see rule 9). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Copacetic &#187; Blog Archive &#187; Stumbleupon kicks in with a traffic spike</title>
		<link>http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-4597</link>
		<dc:creator>Copacetic &#187; Blog Archive &#187; Stumbleupon kicks in with a traffic spike</dc:creator>
		<pubDate>Thu, 14 Sep 2006 19:37:12 +0000</pubDate>
		<guid isPermaLink="false">http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-4597</guid>
		<description>[...] I seem to have hit some weird threshold in stumbleupon for the article Joe&#8217;s Ten Rules of Commercial Software Development. My webstats are up 753% for the article with 137 visitors today. For comparison I usually get about 40 or so visitors per day. Anybody know how stumbleupon works to promote your site? [...]</description>
		<content:encoded><![CDATA[<p>[...] I seem to have hit some weird threshold in stumbleupon for the article Joe&#8217;s Ten Rules of Commercial Software Development. My webstats are up 753% for the article with 137 visitors today. For comparison I usually get about 40 or so visitors per day. Anybody know how stumbleupon works to promote your site? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johnny K</title>
		<link>http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-3376</link>
		<dc:creator>Johnny K</dc:creator>
		<pubDate>Wed, 02 Aug 2006 11:02:15 +0000</pubDate>
		<guid isPermaLink="false">http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-3376</guid>
		<description>There are two of us in the team.  Only one of us refuses to do things.  Guess I'm the asshole ;)</description>
		<content:encoded><![CDATA[<p>There are two of us in the team.  Only one of us refuses to do things.  Guess I&#8217;m the asshole <img src='http://joedrumgoole.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bref Murdoch</title>
		<link>http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-2874</link>
		<dc:creator>Bref Murdoch</dc:creator>
		<pubDate>Thu, 20 Jul 2006 23:21:10 +0000</pubDate>
		<guid isPermaLink="false">http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-2874</guid>
		<description>#9! Ha, every team has an asshole... I think its part of the deal! (anybody in mind?) ... heheehee</description>
		<content:encoded><![CDATA[<p>#9! Ha, every team has an asshole&#8230; I think its part of the deal! (anybody in mind?) &#8230; heheehee</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Navarik : : Ten rules of software development :: The Marine Data Network&#8482;</title>
		<link>http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-2869</link>
		<dc:creator>Navarik : : Ten rules of software development :: The Marine Data Network&#8482;</dc:creator>
		<pubDate>Thu, 20 Jul 2006 19:48:11 +0000</pubDate>
		<guid isPermaLink="false">http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-2869</guid>
		<description>[...] Via Darren Barefoot, here are ten rules of commercial software development. I particular like #7: &#8220;One hour watching a novice user with a new piece of software is worth 24 hours of automated test.&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] Via Darren Barefoot, here are ten rules of commercial software development. I particular like #7: &#8220;One hour watching a novice user with a new piece of software is worth 24 hours of automated test.&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe&#8217;s Ten Rules of Software Development &#124; DarrenBarefoot.com</title>
		<link>http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-2860</link>
		<dc:creator>Joe&#8217;s Ten Rules of Software Development &#124; DarrenBarefoot.com</dc:creator>
		<pubDate>Thu, 20 Jul 2006 16:38:13 +0000</pubDate>
		<guid isPermaLink="false">http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-2860</guid>
		<description>[...] Regardless, he&#8217;s assembled a list of rules for building software to sell to the masses: 100-1: This a good ratio of end-users to developers to aim for as a starting point. With less than this you donâ€™t get feedback and the feedback you do get will tend to take you in strange directions. Remember if you build a stadium you have to fill it every weekend to make a return, software works off similar ratios. [...]</description>
		<content:encoded><![CDATA[<p>[...] Regardless, he&#8217;s assembled a list of rules for building software to sell to the masses: 100-1: This a good ratio of end-users to developers to aim for as a starting point. With less than this you donâ€™t get feedback and the feedback you do get will tend to take you in strange directions. Remember if you build a stadium you have to fill it every weekend to make a return, software works off similar ratios. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darren</title>
		<link>http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-2859</link>
		<dc:creator>Darren</dc:creator>
		<pubDate>Thu, 20 Jul 2006 16:33:10 +0000</pubDate>
		<guid isPermaLink="false">http://joedrumgoole.com/blog/2006/07/19/joes-ten-rules-of-commercial-software-development/#comment-2859</guid>
		<description>By the way, I dugg this badboy:

http://digg.com/software/Ten_Rules_of_Commercial_Software_Development</description>
		<content:encoded><![CDATA[<p>By the way, I dugg this badboy:</p>
<p><a href="http://digg.com/software/Ten_Rules_of_Commercial_Software_Development" rel="nofollow">http://digg.com/software/Ten_Rules_of_Commercial_Software_Development</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
