<?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: Peer Code Reviews: Good Commenting Practices</title>
	<atom:link href="http://scottbilas.com/blog/peer-code-reviews-good-commenting-practices/feed/" rel="self" type="application/rss+xml" />
	<link>http://scottbilas.com/blog/peer-code-reviews-good-commenting-practices/</link>
	<description>Take what you want, and leave the rest (just like your salad bar).</description>
	<lastBuildDate>Tue, 09 Mar 2010 20:13:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Peer Code Reviews: How Did We Do? at New Fun Blog &#8211; Scott Bilas</title>
		<link>http://scottbilas.com/blog/peer-code-reviews-good-commenting-practices/comment-page-1/#comment-290</link>
		<dc:creator>Peer Code Reviews: How Did We Do? at New Fun Blog &#8211; Scott Bilas</dc:creator>
		<pubDate>Wed, 30 Sep 2009 22:09:25 +0000</pubDate>
		<guid isPermaLink="false">http://scottbilas.com/2009/07/26/peer-code-reviews-good-commenting-practices/#comment-290</guid>
		<description>[...] Good Commenting Practices: some best practices for making review comments [...]</description>
		<content:encoded><![CDATA[<p>[...] Good Commenting Practices: some best practices for making review comments [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Code review is code use &#171; Talk About Quality</title>
		<link>http://scottbilas.com/blog/peer-code-reviews-good-commenting-practices/comment-page-1/#comment-222</link>
		<dc:creator>Code review is code use &#171; Talk About Quality</dc:creator>
		<pubDate>Mon, 27 Jul 2009 22:06:29 +0000</pubDate>
		<guid isPermaLink="false">http://scottbilas.com/2009/07/26/peer-code-reviews-good-commenting-practices/#comment-222</guid>
		<description>[...] me to the following post from Scott Bilas at the game software company Loose Cannon Studios. In Peer Code Reviews: Good Commenting Practices, Bilas says code reviewers should seek architectural issues, and adherence to good software [...]</description>
		<content:encoded><![CDATA[<p>[...] me to the following post from Scott Bilas at the game software company Loose Cannon Studios. In Peer Code Reviews: Good Commenting Practices, Bilas says code reviewers should seek architectural issues, and adherence to good software [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
