<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Stephen&#039;s Thoughts &#187; code review</title>
	<atom:link href="http://www.stephendowney.net/blog/category/code-review/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stephendowney.net/blog</link>
	<description>Java &#38; Android Developer &#124; Dublin Ireland</description>
	<lastBuildDate>Mon, 19 Dec 2011 19:33:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>So what are Code Reviews?</title>
		<link>http://www.stephendowney.net/blog/2006/09/11/so-what-are-code-reviews/</link>
		<comments>http://www.stephendowney.net/blog/2006/09/11/so-what-are-code-reviews/#comments</comments>
		<pubDate>Mon, 11 Sep 2006 09:43:27 +0000</pubDate>
		<dc:creator>Stephen Downey</dc:creator>
				<category><![CDATA[article]]></category>
		<category><![CDATA[code review]]></category>
		<category><![CDATA[quality]]></category>

		<guid isPermaLink="false">http://www.stephendowney.net/blog/2006/09/11/so-what-are-code-reviews/</guid>
		<description><![CDATA[I became interested in code reviews while working with Accenture Ireland. As part of my role I was responsible for introducing code reviews into the project and insuring that they took place.&#160; It was amazing to see the difference a 15 minute discussion of a piece of code or a design document could improve the [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.stephendowney.net/blog/wp-content/uploads/codeReviewSite.jpg" border="0" align="right" />
<p>I became interested in code reviews while working with Accenture Ireland.  As part of my role I was responsible for introducing code reviews into the project and insuring that they took place.&nbsp; It was amazing to see the difference a 15 minute discussion of a piece of code or a design document could improve the overall quality of the project.&nbsp; As more people are aware of the design for an early stage.&nbsp; It also serves to educate more junior developers on the team.&nbsp; <a href="http://today.java.net/pub/au/480" target="_blank" title="Srivaths Sankaran">Srivaths Sankaran</a> presents a good overview of code reviews in this article.&nbsp; It will give you a good background in to why we perform Code reviews and the many aspect of a code review. &nbsp; He concludes his article by saying:</p>
<blockquote><p>&#8230;..You <em>can </em>conduct thorough code reviews  without succumbing to time pressures. Did you know that more than 60 percent of  the defects can be captured by effective use of peer reviews (c.f., Boehm and  Basili&#39;s <a href="http://www.cebase.org/www/resources/reports/usc/usccse2001-515.pdf" target="_blank">Software  Defect Reduction Top 10 List</a> )? With a judicious combination of  automation, interactive tools, and risk-based evaluation, you can reap the  benefits of early problem detection&#8230;..</p></blockquote>
<p>One piece of advice I would say is to remember that the primary goal of Code reviews is to improve quality and educate developers. &nbsp; It is <strong>not </strong>a witch hunt!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.stephendowney.net/blog/2006/09/11/so-what-are-code-reviews/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

