<?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: Six Things to Keep in Mind when Considering Code Reviews</title>
	<atom:link href="http://www.icekreamkoan.com/2009/02/17/six-things-to-keep-in-mind-when-considering-code-reviews/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.icekreamkoan.com/2009/02/17/six-things-to-keep-in-mind-when-considering-code-reviews/</link>
	<description>Flying and other stuff - Peter Braswell</description>
	<lastBuildDate>Fri, 13 Aug 2010 22:27:30 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Steve Mixon</title>
		<link>http://www.icekreamkoan.com/2009/02/17/six-things-to-keep-in-mind-when-considering-code-reviews/comment-page-1/#comment-1493</link>
		<dc:creator>Steve Mixon</dc:creator>
		<pubDate>Fri, 06 Mar 2009 23:53:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.icekreamkoan.com/?p=186#comment-1493</guid>
		<description>I have three questions I subject activities to: does it share knowledge, create teamwork and increase efficiency.  Reviews meet that criteria.  I like to spend most effort on designs and design reviews, less on code reviews.  I am a big fan of peer reviews for code.  During the design phase complicated areas can be identified and targeted for code review and magnitude of review.  Also during the design phase, modules targeted for reuse can be identified and given the extra time and quality warranted, implying other code should not be overly designed.

Steve Mixon mixonsr@yahoo.com</description>
		<content:encoded><![CDATA[<p>I have three questions I subject activities to: does it share knowledge, create teamwork and increase efficiency.  Reviews meet that criteria.  I like to spend most effort on designs and design reviews, less on code reviews.  I am a big fan of peer reviews for code.  During the design phase complicated areas can be identified and targeted for code review and magnitude of review.  Also during the design phase, modules targeted for reuse can be identified and given the extra time and quality warranted, implying other code should not be overly designed.</p>
<p>Steve Mixon <a href="mailto:mixonsr@yahoo.com">mixonsr@yahoo.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gregg Sporar</title>
		<link>http://www.icekreamkoan.com/2009/02/17/six-things-to-keep-in-mind-when-considering-code-reviews/comment-page-1/#comment-1491</link>
		<dc:creator>Gregg Sporar</dc:creator>
		<pubDate>Tue, 17 Feb 2009 19:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.icekreamkoan.com/?p=186#comment-1491</guid>
		<description>That&#039;s a good list, especially the part about not spiraling into an endless discussion. FWIW, a while back our company did a study of code review at Cisco - the results are available in a book that we make available for free on our web site: http://smartbear.com/codecollab-code-review-book.php</description>
		<content:encoded><![CDATA[<p>That&#8217;s a good list, especially the part about not spiraling into an endless discussion. FWIW, a while back our company did a study of code review at Cisco &#8211; the results are available in a book that we make available for free on our web site: <a href="http://smartbear.com/codecollab-code-review-book.php" rel="nofollow">http://smartbear.com/codecollab-code-review-book.php</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
