<?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: Book Club: Working Effectively With Legacy Code &#8211; Chapters 6 &amp; 7 (Michael Feathers)</title>
	<atom:link href="http://www.markhneedham.com/blog/2009/10/26/book-club-working-effectively-with-legacy-code-chapters-6-7-michael-feathers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markhneedham.com/blog/2009/10/26/book-club-working-effectively-with-legacy-code-chapters-6-7-michael-feathers/</link>
	<description>Thoughts on Software Development</description>
	<lastBuildDate>Sun, 14 Mar 2010 09:50:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Book Review: Working Effectively with Legacy Code &#8211; Chapter 6 &#171; Dahlia Bock</title>
		<link>http://www.markhneedham.com/blog/2009/10/26/book-club-working-effectively-with-legacy-code-chapters-6-7-michael-feathers/comment-page-1/#comment-26509</link>
		<dc:creator>Book Review: Working Effectively with Legacy Code &#8211; Chapter 6 &#171; Dahlia Bock</dc:creator>
		<pubDate>Tue, 10 Nov 2009 02:41:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=1765#comment-26509</guid>
		<description>[...] Doing the latter isn&#8217;t easy, and in fact it is so hard to achieve that people end up not doing it at all. So that leaves us with Option 1. But sometimes you come across code that doesn&#8217;t have any tests AND doesn&#8217;t look like it is testable, but you have to make some changes in a short amount of time. So what do you do? Michael Feathers suggests 4 approaches, and Mark documents it in a short and sweet way. [...]</description>
		<content:encoded><![CDATA[<p>[...] Doing the latter isn't easy, and in fact it is so hard to achieve that people end up not doing it at all. So that leaves us with Option 1. But sometimes you come across code that doesn't have any tests AND doesn't look like it is testable, but you have to make some changes in a short amount of time. So what do you do? Michael Feathers suggests 4 approaches, and Mark documents it in a short and sweet way. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arjan&#8217;s World &#187; LINKBLOG for Oct 27, 2009</title>
		<link>http://www.markhneedham.com/blog/2009/10/26/book-club-working-effectively-with-legacy-code-chapters-6-7-michael-feathers/comment-page-1/#comment-25506</link>
		<dc:creator>Arjan&#8217;s World &#187; LINKBLOG for Oct 27, 2009</dc:creator>
		<pubDate>Tue, 27 Oct 2009 16:15:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=1765#comment-25506</guid>
		<description>[...] Book Club: Working Effectively With Legacy Code – Chapters 6 &amp; 7 (Michael Feathers) &#8211; Ma... [...]</description>
		<content:encoded><![CDATA[<p>[...] Book Club: Working Effectively With Legacy Code – Chapters 6 &amp; 7 (Michael Feathers) &#8211; Ma&#8230; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
