<?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: 5 tips to make good code reviews</title>
	<atom:link href="http://www.makinggoodsoftware.com/2009/08/06/5-tips-to-make-good-code-reviews/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.makinggoodsoftware.com/2009/08/06/5-tips-to-make-good-code-reviews/</link>
	<description></description>
	<lastBuildDate>Fri, 03 Feb 2012 13:13:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Top 7 programmers bad habits &#187; OnnoRokom</title>
		<link>http://www.makinggoodsoftware.com/2009/08/06/5-tips-to-make-good-code-reviews/comment-page-1/#comment-55328</link>
		<dc:creator>Top 7 programmers bad habits &#187; OnnoRokom</dc:creator>
		<pubDate>Sat, 11 Jun 2011 05:29:12 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=363#comment-55328</guid>
		<description>[...] training. Probably the two easiest ways to help a programmer understand if some code is done are  peer reviews and [...]</description>
		<content:encoded><![CDATA[<p>[...] training. Probably the two easiest ways to help a programmer understand if some code is done are  peer reviews and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomalak Geret'kal</title>
		<link>http://www.makinggoodsoftware.com/2009/08/06/5-tips-to-make-good-code-reviews/comment-page-1/#comment-53437</link>
		<dc:creator>Tomalak Geret'kal</dc:creator>
		<pubDate>Tue, 31 May 2011 09:53:34 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=363#comment-53437</guid>
		<description>Josef,

If you need to sign-off five minutes&#039; code review time with higher management, you have a micro-management problem in your company.</description>
		<content:encoded><![CDATA[<p>Josef,</p>
<p>If you need to sign-off five minutes&#8217; code review time with higher management, you have a micro-management problem in your company.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kashif Baig</title>
		<link>http://www.makinggoodsoftware.com/2009/08/06/5-tips-to-make-good-code-reviews/comment-page-1/#comment-7971</link>
		<dc:creator>Kashif Baig</dc:creator>
		<pubDate>Sat, 29 May 2010 15:30:20 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=363#comment-7971</guid>
		<description>Nice article. I would add that formal audits need to be done too, but not as frequently as informal audits.

Design best practices and coding standards should be part of checklist - automated tools will only go so far.</description>
		<content:encoded><![CDATA[<p>Nice article. I would add that formal audits need to be done too, but not as frequently as informal audits.</p>
<p>Design best practices and coding standards should be part of checklist &#8211; automated tools will only go so far.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: My favorite Software Testing blogs &#124; Fred Beringer</title>
		<link>http://www.makinggoodsoftware.com/2009/08/06/5-tips-to-make-good-code-reviews/comment-page-1/#comment-1166</link>
		<dc:creator>My favorite Software Testing blogs &#124; Fred Beringer</dc:creator>
		<pubDate>Fri, 18 Sep 2009 14:28:35 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=363#comment-1166</guid>
		<description>[...] Making good software – Alberto Gutierrez 5 tips to make good code reviews  Test obsessed &#8211; Elisabeth Hendrickson The wordCount simulation  utest.com official blog Testing the limits  TestMechanics &#8211; Jitendra Kapoor Becoming an indispensable tester [...]</description>
		<content:encoded><![CDATA[<p>[...] Making good software – Alberto Gutierrez 5 tips to make good code reviews  Test obsessed &#8211; Elisabeth Hendrickson The wordCount simulation  utest.com official blog Testing the limits  TestMechanics &#8211; Jitendra Kapoor Becoming an indispensable tester [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 網站製作學習誌 &#187; [Web] 連結分享</title>
		<link>http://www.makinggoodsoftware.com/2009/08/06/5-tips-to-make-good-code-reviews/comment-page-1/#comment-949</link>
		<dc:creator>網站製作學習誌 &#187; [Web] 連結分享</dc:creator>
		<pubDate>Tue, 01 Sep 2009 12:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=363#comment-949</guid>
		<description>[...] 5 tips to make good code reviews [...]</description>
		<content:encoded><![CDATA[<p>[...] 5 tips to make good code reviews [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Interesting Finds: 2009 08.19 ~ 08.25 - gOODiDEA.NET</title>
		<link>http://www.makinggoodsoftware.com/2009/08/06/5-tips-to-make-good-code-reviews/comment-page-1/#comment-882</link>
		<dc:creator>Interesting Finds: 2009 08.19 ~ 08.25 - gOODiDEA.NET</dc:creator>
		<pubDate>Tue, 25 Aug 2009 01:47:47 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=363#comment-882</guid>
		<description>[...] 5 tips to make good code reviews [...]</description>
		<content:encoded><![CDATA[<p>[...] 5 tips to make good code reviews [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Weekly Link Post 107 &#171; Rhonda Tipton&#8217;s WebLog</title>
		<link>http://www.makinggoodsoftware.com/2009/08/06/5-tips-to-make-good-code-reviews/comment-page-1/#comment-872</link>
		<dc:creator>Weekly Link Post 107 &#171; Rhonda Tipton&#8217;s WebLog</dc:creator>
		<pubDate>Mon, 24 Aug 2009 00:12:39 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=363#comment-872</guid>
		<description>[...] 5 tips to make good code reviews &#8212; Code reviews are one of the most valuable engineering practices. [...]</description>
		<content:encoded><![CDATA[<p>[...] 5 tips to make good code reviews &#8212; Code reviews are one of the most valuable engineering practices. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alberto Gutierrez</title>
		<link>http://www.makinggoodsoftware.com/2009/08/06/5-tips-to-make-good-code-reviews/comment-page-1/#comment-867</link>
		<dc:creator>Alberto Gutierrez</dc:creator>
		<pubDate>Sun, 23 Aug 2009 00:16:50 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=363#comment-867</guid>
		<description>You are actually making a very good point here Gregg, I agree with you 100%, automated tests will NEVER cover 100% of your bugs, that&#039;s why, as you say, you also need to review your automated code as well. good observation!</description>
		<content:encoded><![CDATA[<p>You are actually making a very good point here Gregg, I agree with you 100%, automated tests will NEVER cover 100% of your bugs, that&#8217;s why, as you say, you also need to review your automated code as well. good observation!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gregg Sporar</title>
		<link>http://www.makinggoodsoftware.com/2009/08/06/5-tips-to-make-good-code-reviews/comment-page-1/#comment-864</link>
		<dc:creator>Gregg Sporar</dc:creator>
		<pubDate>Sat, 22 Aug 2009 17:26:27 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=363#comment-864</guid>
		<description>All good advice, but I&#039;m having a bit of trouble believing that finding errors in the code can always be &quot; covered by your automated tests.&quot; 

At the very least, it seems the automated test code should be reviewed in order to make sure that *it* is correct.  No static analysis tool can detect whether the software really solves the problem it was intended to solve.</description>
		<content:encoded><![CDATA[<p>All good advice, but I&#8217;m having a bit of trouble believing that finding errors in the code can always be &#8221; covered by your automated tests.&#8221; </p>
<p>At the very least, it seems the automated test code should be reviewed in order to make sure that *it* is correct.  No static analysis tool can detect whether the software really solves the problem it was intended to solve.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2009-08-22 &#171; pabloidz</title>
		<link>http://www.makinggoodsoftware.com/2009/08/06/5-tips-to-make-good-code-reviews/comment-page-1/#comment-861</link>
		<dc:creator>links for 2009-08-22 &#171; pabloidz</dc:creator>
		<pubDate>Sat, 22 Aug 2009 12:02:28 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=363#comment-861</guid>
		<description>[...] 5 tips to make good code reviews Making Good Software (tags: agile programming) [...]</description>
		<content:encoded><![CDATA[<p>[...] 5 tips to make good code reviews Making Good Software (tags: agile programming) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

