<?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: Why do Code Reviews Matter?</title>
	<atom:link href="http://blog.burcudogan.com/292/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.burcudogan.com/292/</link>
	<description>burcu dogan&#039;s monthly routine. caution: risk of overdose.</description>
	<lastBuildDate>Fri, 18 Jun 2010 14:52:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Ozan Akcora</title>
		<link>http://blog.burcudogan.com/292/comment-page-1/#comment-3418</link>
		<dc:creator>Ozan Akcora</dc:creator>
		<pubDate>Thu, 29 Oct 2009 22:37:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.burcudogan.com/?p=292#comment-3418</guid>
		<description>Hola,

QA tests are not ignorable but unfortunately there are so many websites there are built on one&#039;s hand. It causes code to be unreadable, not extensible and not even stable. But i think TDD is really important on development and also QA testing. If you wanna do agile development, you need to have something watch your back =) Or be ready for the sleepless nights =)

BTW, @Burcu, i want to congratulate you for this blog and sharing.</description>
		<content:encoded><![CDATA[<p>Hola,</p>
<p>QA tests are not ignorable but unfortunately there are so many websites there are built on one&#8217;s hand. It causes code to be unreadable, not extensible and not even stable. But i think TDD is really important on development and also QA testing. If you wanna do agile development, you need to have something watch your back =) Or be ready for the sleepless nights =)</p>
<p>BTW, @Burcu, i want to congratulate you for this blog and sharing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Burcu Dogan</title>
		<link>http://blog.burcudogan.com/292/comment-page-1/#comment-3233</link>
		<dc:creator>Burcu Dogan</dc:creator>
		<pubDate>Tue, 13 Oct 2009 07:11:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.burcudogan.com/?p=292#comment-3233</guid>
		<description>kuzushi, I tend to believe there is no &quot;fast&quot; software development but fast adoption to changes in specs. No one believes but I&#039;ve seen people who thinks agile is coding where you dont have to leave documentation in code, such as commenting. In fact, agile is the most systematic way of software development, automating the whole release cycle and be able to determine what is being affected as fast as possible.</description>
		<content:encoded><![CDATA[<p>kuzushi, I tend to believe there is no &#8220;fast&#8221; software development but fast adoption to changes in specs. No one believes but I&#8217;ve seen people who thinks agile is coding where you dont have to leave documentation in code, such as commenting. In fact, agile is the most systematic way of software development, automating the whole release cycle and be able to determine what is being affected as fast as possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kuzushi</title>
		<link>http://blog.burcudogan.com/292/comment-page-1/#comment-3229</link>
		<dc:creator>kuzushi</dc:creator>
		<pubDate>Tue, 13 Oct 2009 05:28:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.burcudogan.com/?p=292#comment-3229</guid>
		<description>@Burcu:  Actually, TDD is slower almost always.  Microsoft has done a bunch of research into the matter and you can read all their cool findings here: http://bit.ly/163eOW

The upside however is that it&#039;s also almost always better quality.  

-A</description>
		<content:encoded><![CDATA[<p>@Burcu:  Actually, TDD is slower almost always.  Microsoft has done a bunch of research into the matter and you can read all their cool findings here: <a href="http://bit.ly/163eOW" rel="nofollow">http://bit.ly/163eOW</a></p>
<p>The upside however is that it&#8217;s also almost always better quality.  </p>
<p>-A</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Burcu Dogan</title>
		<link>http://blog.burcudogan.com/292/comment-page-1/#comment-2815</link>
		<dc:creator>Burcu Dogan</dc:creator>
		<pubDate>Wed, 09 Sep 2009 11:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.burcudogan.com/?p=292#comment-2815</guid>
		<description>Development should be test driven. The more you automate the release pipeline, the faster you develop. In cases where small teams develop small scale products for a very limited time span, this is often avoided. Most of the industry (small scale companies) cannot afford to write their own continuous integration tools and scripts. This is still an unsolved issue in the small scale.</description>
		<content:encoded><![CDATA[<p>Development should be test driven. The more you automate the release pipeline, the faster you develop. In cases where small teams develop small scale products for a very limited time span, this is often avoided. Most of the industry (small scale companies) cannot afford to write their own continuous integration tools and scripts. This is still an unsolved issue in the small scale.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ali Muhtaki</title>
		<link>http://blog.burcudogan.com/292/comment-page-1/#comment-2787</link>
		<dc:creator>Ali Muhtaki</dc:creator>
		<pubDate>Mon, 07 Sep 2009 12:43:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.burcudogan.com/?p=292#comment-2787</guid>
		<description>What is your view on TDD?</description>
		<content:encoded><![CDATA[<p>What is your view on TDD?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ali Muhtaki</title>
		<link>http://blog.burcudogan.com/292/comment-page-1/#comment-2786</link>
		<dc:creator>Ali Muhtaki</dc:creator>
		<pubDate>Mon, 07 Sep 2009 11:38:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.burcudogan.com/?p=292#comment-2786</guid>
		<description>Most expert programmers love pair programming. It is a very effective coaching tool. The result code is twice as high quality as the code you would write alone. But I agree it is not suitable for everyone. A good programmer should be open to criticism and should not take critics personally. What the pairs try to achieve is the best quality code possible and they will both be succesfull if they achieve that. There is no &quot;I&quot; in a team.!</description>
		<content:encoded><![CDATA[<p>Most expert programmers love pair programming. It is a very effective coaching tool. The result code is twice as high quality as the code you would write alone. But I agree it is not suitable for everyone. A good programmer should be open to criticism and should not take critics personally. What the pairs try to achieve is the best quality code possible and they will both be succesfull if they achieve that. There is no &#8220;I&#8221; in a team.!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Burcu Dogan</title>
		<link>http://blog.burcudogan.com/292/comment-page-1/#comment-2773</link>
		<dc:creator>Burcu Dogan</dc:creator>
		<pubDate>Sun, 06 Sep 2009 19:47:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.burcudogan.com/?p=292#comment-2773</guid>
		<description>Pair programming seems to be an applicable solution but we are humans, not machines. Most of the developers like to write alone in a personal and silent environment - such as home. I personally couldnt write a single line of code if someone was reviewing me. It&#039;s very uncomfortable. I dont have the scientific facts about the effectiveness of pair programming, but it&#039;s a no-no for me.</description>
		<content:encoded><![CDATA[<p>Pair programming seems to be an applicable solution but we are humans, not machines. Most of the developers like to write alone in a personal and silent environment &#8211; such as home. I personally couldnt write a single line of code if someone was reviewing me. It&#8217;s very uncomfortable. I dont have the scientific facts about the effectiveness of pair programming, but it&#8217;s a no-no for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ali Muhtaki</title>
		<link>http://blog.burcudogan.com/292/comment-page-1/#comment-2731</link>
		<dc:creator>Ali Muhtaki</dc:creator>
		<pubDate>Fri, 04 Sep 2009 06:24:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.burcudogan.com/?p=292#comment-2731</guid>
		<description>What do you think about &quot;Pair Programming&quot; with respect to Code reviews?</description>
		<content:encoded><![CDATA[<p>What do you think about &#8220;Pair Programming&#8221; with respect to Code reviews?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ali Servet Donmez</title>
		<link>http://blog.burcudogan.com/292/comment-page-1/#comment-2721</link>
		<dc:creator>Ali Servet Donmez</dc:creator>
		<pubDate>Thu, 03 Sep 2009 15:15:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.burcudogan.com/?p=292#comment-2721</guid>
		<description>Great words, unfortunately most small teams won&#039;t have enough resources (or will) to follow these guidelines and end up with messy code in short time.</description>
		<content:encoded><![CDATA[<p>Great words, unfortunately most small teams won&#8217;t have enough resources (or will) to follow these guidelines and end up with messy code in short time.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
