<?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: Strategies for Effective Code Reviews</title>
	<atom:link href="http://www.basilv.com/psd/blog/2007/strategies-for-effective-code-reviews/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.basilv.com/psd/blog/2007/strategies-for-effective-code-reviews</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 03:57:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Linda</title>
		<link>http://www.basilv.com/psd/blog/2007/strategies-for-effective-code-reviews/comment-page-1#comment-110463</link>
		<dc:creator>Linda</dc:creator>
		<pubDate>Mon, 02 Aug 2010 08:21:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.basilv.com/psd/blog/2007/strategies-for-effective-code-reviews#comment-110463</guid>
		<description>I definitely agree about commenting your code. *Especially* if it&#039;s going to be shared.

One thing that has served me well is to simply keep a journal about WHY a change was made. A daily journal to keep notes. Handing a new developer a journal will allow them to get up to speed on the logic side side of things.

Great article though! Very in-depth!</description>
		<content:encoded><![CDATA[<p>I definitely agree about commenting your code. *Especially* if it&#8217;s going to be shared.</p>
<p>One thing that has served me well is to simply keep a journal about WHY a change was made. A daily journal to keep notes. Handing a new developer a journal will allow them to get up to speed on the logic side side of things.</p>
<p>Great article though! Very in-depth!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pravin Sharma</title>
		<link>http://www.basilv.com/psd/blog/2007/strategies-for-effective-code-reviews/comment-page-1#comment-80349</link>
		<dc:creator>Pravin Sharma</dc:creator>
		<pubDate>Thu, 12 Feb 2009 10:58:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.basilv.com/psd/blog/2007/strategies-for-effective-code-reviews#comment-80349</guid>
		<description>This is really nice article. It should also explain with examples so that it will become more effective</description>
		<content:encoded><![CDATA[<p>This is really nice article. It should also explain with examples so that it will become more effective</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Infovore &#187; links for 2007-10-08</title>
		<link>http://www.basilv.com/psd/blog/2007/strategies-for-effective-code-reviews/comment-page-1#comment-31360</link>
		<dc:creator>Infovore &#187; links for 2007-10-08</dc:creator>
		<pubDate>Mon, 08 Oct 2007 23:20:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.basilv.com/psd/blog/2007/strategies-for-effective-code-reviews#comment-31360</guid>
		<description>[...] Professional Software Development » Strategies for Effective Code Reviews &#8220;You need to mentally prepare yourself before starting a review by reminding yourself of the purpose of the review and the need for a critical, questioning attitude.&#8221; Nice article on how to make code reviews effective. (tags: code review software development programming practice) [...]</description>
		<content:encoded><![CDATA[<p>[...] Professional Software Development » Strategies for Effective Code Reviews &#8220;You need to mentally prepare yourself before starting a review by reminding yourself of the purpose of the review and the need for a critical, questioning attitude.&#8221; Nice article on how to make code reviews effective. (tags: code review software development programming practice) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

