<?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: Effective Technology Teams: Rule #1, No Chumps</title>
	<atom:link href="http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/</link>
	<description>Ruminations about innovation and software by Rob Di Marco</description>
	<pubDate>Wed, 07 Jan 2009 06:55:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: No Rock Stars Need Apply &#124; Innovation On The Run</title>
		<link>http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/comment-page-1/#comment-240</link>
		<dc:creator>No Rock Stars Need Apply &#124; Innovation On The Run</dc:creator>
		<pubDate>Thu, 23 Oct 2008 13:35:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/#comment-240</guid>
		<description>[...] i talked about in Effective Technology Teams, what someone knows is much less important than what they can learn.&#160; For further reading, I [...]</description>
		<content:encoded><![CDATA[<p>[...] i talked about in Effective Technology Teams, what someone knows is much less important than what they can learn.&nbsp; For further reading, I [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Di Marco</title>
		<link>http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/comment-page-1/#comment-139</link>
		<dc:creator>Rob Di Marco</dc:creator>
		<pubDate>Mon, 31 Mar 2008 02:46:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/#comment-139</guid>
		<description>Marge, thank you for your grammatical pointers.  I will edit accordingly.</description>
		<content:encoded><![CDATA[<p>Marge, thank you for your grammatical pointers.  I will edit accordingly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marge</title>
		<link>http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/comment-page-1/#comment-138</link>
		<dc:creator>Marge</dc:creator>
		<pubDate>Mon, 31 Mar 2008 02:00:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/#comment-138</guid>
		<description>This post is very well helpful, and I'm sure, very well thought out.  However, it is also a testament to how difficult it is to catch one's own mistakes, as it does contain several typos, in spite of the author's stated abhorrence to such oversights:

1)  "Has their been any book/website/blog that has made you think differently about how you should work?"  It should be "Has there . . . "

2)  "The goal is to get great hires and avoid chumps, it is not a time to take big risks."  The commas should be a semi-colon or a period, with a new sentence starting at "it."

3)  "Not necessarily, it just means that we weren’t positive that you were great."  Just like #2 above, the comma should be a semi-colon or a period, with a new sentence starting at "it."

I have found that asking another to read my work, or setting it aside for a day or two, and then rereading, helps me to avoid those abhorrent typos.  With online documents, printing them out helps me to find those typos, although this is more difficult with blogs.</description>
		<content:encoded><![CDATA[<p>This post is very well helpful, and I&#8217;m sure, very well thought out.  However, it is also a testament to how difficult it is to catch one&#8217;s own mistakes, as it does contain several typos, in spite of the author&#8217;s stated abhorrence to such oversights:</p>
<p>1)  &#8220;Has their been any book/website/blog that has made you think differently about how you should work?&#8221;  It should be &#8220;Has there . . . &#8221;</p>
<p>2)  &#8220;The goal is to get great hires and avoid chumps, it is not a time to take big risks.&#8221;  The commas should be a semi-colon or a period, with a new sentence starting at &#8220;it.&#8221;</p>
<p>3)  &#8220;Not necessarily, it just means that we weren’t positive that you were great.&#8221;  Just like #2 above, the comma should be a semi-colon or a period, with a new sentence starting at &#8220;it.&#8221;</p>
<p>I have found that asking another to read my work, or setting it aside for a day or two, and then rereading, helps me to avoid those abhorrent typos.  With online documents, printing them out helps me to find those typos, although this is more difficult with blogs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: StumbleUpon &#187; Your page is now on StumbleUpon!</title>
		<link>http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/comment-page-1/#comment-90</link>
		<dc:creator>StumbleUpon &#187; Your page is now on StumbleUpon!</dc:creator>
		<pubDate>Sat, 01 Dec 2007 11:52:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/#comment-90</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] Your page is on StumbleUpon [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><!--%kramer-ref-pre%-->[...] Your page is on StumbleUpon [...]<!--%kramer-ref-post%--></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LinkMoTron v0.987</title>
		<link>http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/comment-page-1/#comment-25</link>
		<dc:creator>LinkMoTron v0.987</dc:creator>
		<pubDate>Tue, 14 Aug 2007 11:51:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/#comment-25</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] Effective Technology Teams: Rule #1, No Chumps [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><!--%kramer-ref-pre%-->[...] Effective Technology Teams: Rule #1, No Chumps [...]<!--%kramer-ref-post%--></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A few good links &#171; Silent Walker</title>
		<link>http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/comment-page-1/#comment-24</link>
		<dc:creator>A few good links &#171; Silent Walker</dc:creator>
		<pubDate>Mon, 13 Aug 2007 06:47:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/#comment-24</guid>
		<description>[...] I didn&#8217;t find this one much interesting (but some might). What I did like was a post about building effective team. The article was written for hiring people, what to look into a prospective interviewee to ensure [...]</description>
		<content:encoded><![CDATA[<p>[...] I didn&#8217;t find this one much interesting (but some might). What I did like was a post about building effective team. The article was written for hiring people, what to look into a prospective interviewee to ensure [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandro</title>
		<link>http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/comment-page-1/#comment-23</link>
		<dc:creator>Sandro</dc:creator>
		<pubDate>Sun, 12 Aug 2007 19:30:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/#comment-23</guid>
		<description>Excellent post, as someone who at times doubts their ability to land a programming gig I find your list of basic criteria reassuring.</description>
		<content:encoded><![CDATA[<p>Excellent post, as someone who at times doubts their ability to land a programming gig I find your list of basic criteria reassuring.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TechnicalPickles: Interviewing Research: Links for 08-08-2007</title>
		<link>http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/comment-page-1/#comment-21</link>
		<dc:creator>TechnicalPickles: Interviewing Research: Links for 08-08-2007</dc:creator>
		<pubDate>Wed, 08 Aug 2007 16:16:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/#comment-21</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] Effective Technology Teams: Rule #1, No Chumps Covers some heurestics and other techniques for shifting through the medicore developers. [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><!--%kramer-ref-pre%-->[...] Effective Technology Teams: Rule #1, No Chumps Covers some heurestics and other techniques for shifting through the medicore developers. [...]<!--%kramer-ref-post%--></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A Software Hiring Manifesto</title>
		<link>http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/comment-page-1/#comment-19</link>
		<dc:creator>A Software Hiring Manifesto</dc:creator>
		<pubDate>Wed, 08 Aug 2007 04:47:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/#comment-19</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] rob_dimarco via innovationontherun.com Submitted: Aug 08 / 00:28        A Software Hiring Manifesto This manifesto describes what attributes to look for when hiring programmers, why the attributes [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><!--%kramer-ref-pre%-->[...] rob_dimarco via innovationontherun.com Submitted: Aug 08 / 00:28        A Software Hiring Manifesto This manifesto describes what attributes to look for when hiring programmers, why the attributes [...]<!--%kramer-ref-post%--></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Open Source Software as a Marketing Platform for Hiring &#124; Innovation On The Run</title>
		<link>http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/comment-page-1/#comment-14</link>
		<dc:creator>Open Source Software as a Marketing Platform for Hiring &#124; Innovation On The Run</dc:creator>
		<pubDate>Mon, 23 Jul 2007 23:37:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.innovationontherun.com/effective-technology-teams-rule-1-no-chumps/#comment-14</guid>
		<description>[...] should work for you rather than working for someone else).&#160; From our previous discussion on building teams,&#160;I know that you are looking to hire great developers so they will shortly have multiple job [...]</description>
		<content:encoded><![CDATA[<p>[...] should work for you rather than working for someone else).&nbsp; From our previous discussion on building teams,&nbsp;I know that you are looking to hire great developers so they will shortly have multiple job [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
