<?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: Focusing on Value</title>
	<atom:link href="http://www.udidahan.com/2006/02/08/focusing-on-value/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.udidahan.com/2006/02/08/focusing-on-value/</link>
	<description>Enterprise Development Expert &#38; SOA Specialist</description>
	<lastBuildDate>Sat, 11 Feb 2012 15:16:10 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Yoni Rapoport</title>
		<link>http://www.udidahan.com/2006/02/08/focusing-on-value/comment-page-1/#comment-275</link>
		<dc:creator>Yoni Rapoport</dc:creator>
		<pubDate>Sun, 12 Feb 2006 04:45:29 +0000</pubDate>
		<guid isPermaLink="false">http://wp_630.weblogs.us/archives/253#comment-275</guid>
		<description>Runtime flexibility with DI is, to me, the best way to achieve code reuse in an OO way. When you code your implementation to work with an interface it is easy to reuse by simply re-implementing the interface. Making the implementation easy to test with mock objects is, to me, a mere secondary objective.
</description>
		<content:encoded><![CDATA[<p>Runtime flexibility with DI is, to me, the best way to achieve code reuse in an OO way. When you code your implementation to work with an interface it is easy to reuse by simply re-implementing the interface. Making the implementation easy to test with mock objects is, to me, a mere secondary objective.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

