<?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: Guide: Writing Testable Code</title>
	<atom:link href="http://misko.hevery.com/code-reviewers-guide/feed/" rel="self" type="application/rss+xml" />
	<link>http://misko.hevery.com</link>
	<description>Testability Explorer</description>
	<lastBuildDate>Thu, 02 Sep 2010 04:05:01 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Linking to Mi?ko&#8217;s, Russ&#8217; and my Testability Guide at JAW Speak</title>
		<link>http://misko.hevery.com/code-reviewers-guide/comment-page-2/#comment-3594</link>
		<dc:creator>Linking to Mi?ko&#8217;s, Russ&#8217; and my Testability Guide at JAW Speak</dc:creator>
		<pubDate>Tue, 08 Jun 2010 04:59:08 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=310#comment-3594</guid>
		<description>[...] had the great pleasure of collaborating with Mi?ko Hevery and Russ Rufer in creating the Guide for Writing Testable Code. Please feel free to check it out, and leave comments here or on his [...]</description>
		<content:encoded><![CDATA[<p>[...] had the great pleasure of collaborating with Mi?ko Hevery and Russ Rufer in creating the Guide for Writing Testable Code. Please feel free to check it out, and leave comments here or on his [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Giorgio Bozio</title>
		<link>http://misko.hevery.com/code-reviewers-guide/comment-page-2/#comment-3337</link>
		<dc:creator>Giorgio Bozio</dc:creator>
		<pubDate>Sun, 11 Apr 2010 10:15:42 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=310#comment-3337</guid>
		<description>Thanks for the guide, very good practices! I&#039;ve applied some of the concepts in a blog post, with samples in C#. http://letsfollowtheyellowbrickroad.blogspot.com/2010/04/unit-testing-really.html</description>
		<content:encoded><![CDATA[<p>Thanks for the guide, very good practices! I&#8217;ve applied some of the concepts in a blog post, with samples in C#. <a href="http://letsfollowtheyellowbrickroad.blogspot.com/2010/04/unit-testing-really.html" rel="nofollow">http://letsfollowtheyellowbrickroad.blogspot.com/2010/04/unit-testing-really.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 有效的测试者 &#187; Blog Archive &#187; 指南：如何写出易测试代码</title>
		<link>http://misko.hevery.com/code-reviewers-guide/comment-page-2/#comment-3215</link>
		<dc:creator>有效的测试者 &#187; Blog Archive &#187; 指南：如何写出易测试代码</dc:creator>
		<pubDate>Sat, 20 Mar 2010 16:01:38 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=310#comment-3215</guid>
		<description>[...] Google 工程师 Miško Hevery 写了一篇关于如何将Java代码写的易于单元测试的指南。大量使用依赖注入，使代码更加灵活并容易测试。值得一读。 [...]</description>
		<content:encoded><![CDATA[<p>[...] Google 工程师 Miško Hevery 写了一篇关于如何将Java代码写的易于单元测试的指南。大量使用依赖注入，使代码更加灵活并容易测试。值得一读。 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A useful rule-of-thumb for Law of Demeter violations? at Jason&#8217;s Notebook</title>
		<link>http://misko.hevery.com/code-reviewers-guide/comment-page-2/#comment-3111</link>
		<dc:creator>A useful rule-of-thumb for Law of Demeter violations? at Jason&#8217;s Notebook</dc:creator>
		<pubDate>Mon, 22 Feb 2010 18:20:14 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=310#comment-3111</guid>
		<description>[...] at things I&#8217;ve put aside during busy times.  Right now I&#8217;m finally reading through Writing Testable Code by the Google people.  It&#8217;s good, if a little Google-centric (lots of references to Guice as [...]</description>
		<content:encoded><![CDATA[<p>[...] at things I&#8217;ve put aside during busy times.  Right now I&#8217;m finally reading through Writing Testable Code by the Google people.  It&#8217;s good, if a little Google-centric (lots of references to Guice as [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Writing Testable Code 1/4&#160;&#124;&#160;Private.altprog.com Blogs</title>
		<link>http://misko.hevery.com/code-reviewers-guide/comment-page-2/#comment-3075</link>
		<dc:creator>Writing Testable Code 1/4&#160;&#124;&#160;Private.altprog.com Blogs</dc:creator>
		<pubDate>Sat, 13 Feb 2010 13:38:51 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=310#comment-3075</guid>
		<description>[...] Google에서 사용하는 코딩 가이드라인이 있네요. 테스트하기 좋은 코드를 만들기 위한 가이드라인으로 크게 4가지 얘기를 하고 있습니다. 바쁘고 영어 싫어하시는 분들을 위해서 간단히 정리해보겠습니다. 원문은 아래 주소에서 보세요~&#160; http://misko.hevery.com/code-reviewers-guide/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Google에서 사용하는 코딩 가이드라인이 있네요. 테스트하기 좋은 코드를 만들기 위한 가이드라인으로 크게 4가지 얘기를 하고 있습니다. 바쁘고 영어 싫어하시는 분들을 위해서 간단히 정리해보겠습니다. 원문은 아래 주소에서 보세요~&nbsp; <a href="http://misko.hevery.com/code-reviewers-guide/" rel="nofollow">http://misko.hevery.com/code-reviewers-guide/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Niceboomer and the future of changes &#187; Blog Archive &#187; Guide: Writing Testable Code</title>
		<link>http://misko.hevery.com/code-reviewers-guide/comment-page-2/#comment-3068</link>
		<dc:creator>Niceboomer and the future of changes &#187; Blog Archive &#187; Guide: Writing Testable Code</dc:creator>
		<pubDate>Fri, 12 Feb 2010 20:51:31 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=310#comment-3068</guid>
		<description>[...] Flaw #1: Constructor does Real Work [...]</description>
		<content:encoded><![CDATA[<p>[...] Flaw #1: Constructor does Real Work [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mohan Arun L</title>
		<link>http://misko.hevery.com/code-reviewers-guide/comment-page-2/#comment-2783</link>
		<dc:creator>Mohan Arun L</dc:creator>
		<pubDate>Sat, 09 Jan 2010 10:30:25 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=310#comment-2783</guid>
		<description>Software are like plants. For Growing them you need to put in lot of efforts in the form of naming variables conspicuously and understandably, and follow several other guidelines (coding conventions). Your work is a must-ref for writing testable code. Thanks for making into it a readable and printable pdf format!</description>
		<content:encoded><![CDATA[<p>Software are like plants. For Growing them you need to put in lot of efforts in the form of naming variables conspicuously and understandably, and follow several other guidelines (coding conventions). Your work is a must-ref for writing testable code. Thanks for making into it a readable and printable pdf format!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Einführung in TDD &#38; Clean Code Talks &#124; geekcloud.org</title>
		<link>http://misko.hevery.com/code-reviewers-guide/comment-page-1/#comment-2428</link>
		<dc:creator>Einführung in TDD &#38; Clean Code Talks &#124; geekcloud.org</dc:creator>
		<pubDate>Sun, 22 Nov 2009 14:52:38 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=310#comment-2428</guid>
		<description>[...] gleichem Zuge ist der Guide &#8220;Write Testable Code&#8221; eine gute Quelle. Dieser besteht aus für vier Artikeln, welche man auch zusammengefasst als PDF [...]</description>
		<content:encoded><![CDATA[<p>[...] gleichem Zuge ist der Guide &#8220;Write Testable Code&#8221; eine gute Quelle. Dieser besteht aus für vier Artikeln, welche man auch zusammengefasst als PDF [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://misko.hevery.com/code-reviewers-guide/comment-page-1/#comment-2018</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Mon, 05 Oct 2009 21:42:14 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=310#comment-2018</guid>
		<description>Very nice, there is just one typo,
in the PDF page 20, the constructor UpdateBug under &quot;After: Testable and Flexible Design&quot; doesn&#039;t initialize 
this.lock = lock;</description>
		<content:encoded><![CDATA[<p>Very nice, there is just one typo,<br />
in the PDF page 20, the constructor UpdateBug under &#8220;After: Testable and Flexible Design&#8221; doesn&#8217;t initialize<br />
this.lock = lock;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Testability: How much logic belongs in the constructor? &#171; Alexandre Gazola</title>
		<link>http://misko.hevery.com/code-reviewers-guide/comment-page-1/#comment-1928</link>
		<dc:creator>Testability: How much logic belongs in the constructor? &#171; Alexandre Gazola</dc:creator>
		<pubDate>Wed, 23 Sep 2009 22:35:45 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=310#comment-1928</guid>
		<description>[...] that do nothing other than making simple assignments to fields. As Misko Hevery comments on his Guide for Writing Testable Code, constructors should do no real work. Mark Needham, in turn, advocates the simplification of [...]</description>
		<content:encoded><![CDATA[<p>[...] that do nothing other than making simple assignments to fields. As Misko Hevery comments on his Guide for Writing Testable Code, constructors should do no real work. Mark Needham, in turn, advocates the simplification of [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
