<?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: Udi&#8217;s first principle of design</title>
	<atom:link href="http://www.udidahan.com/2006/01/29/udis-first-principle-of-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.udidahan.com/2006/01/29/udis-first-principle-of-design/</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: Ralf</title>
		<link>http://www.udidahan.com/2006/01/29/udis-first-principle-of-design/comment-page-1/#comment-274</link>
		<dc:creator>Ralf</dc:creator>
		<pubDate>Mon, 30 Jan 2006 13:09:49 +0000</pubDate>
		<guid isPermaLink="false">http://wp_630.weblogs.us/archives/250#comment-274</guid>
		<description>Do you really mean &quot;any classes&quot;? I think that´s not necessary and not feasible. Interface types are like standards: There are standards (e.g. HTTP, RSS) where decoupling is needed, e.g. between client and server software on the web. But there are no standards constraining how you structure your client/server internally.

Likewise there don´t need to be interfaces between each and every class. Rather it´s necessary to identify lumps of code which can be seen as black boxes between which interfaces/contracts are necessary - but within which you can do pretty much all you like ;-)

Nevertheless I´m eager to see your next rules. It´s a worthwhile undertaking trying to structure your knowledge into rules to make it more explicit, because thereby you make it easier to transfer. And you make it easier to discuss ;-)
</description>
		<content:encoded><![CDATA[<p>Do you really mean &#8220;any classes&#8221;? I think that´s not necessary and not feasible. Interface types are like standards: There are standards (e.g. HTTP, RSS) where decoupling is needed, e.g. between client and server software on the web. But there are no standards constraining how you structure your client/server internally.</p>
<p>Likewise there don´t need to be interfaces between each and every class. Rather it´s necessary to identify lumps of code which can be seen as black boxes between which interfaces/contracts are necessary &#8211; but within which you can do pretty much all you like <img src='http://www.udidahan.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Nevertheless I´m eager to see your next rules. It´s a worthwhile undertaking trying to structure your knowledge into rules to make it more explicit, because thereby you make it easier to transfer. And you make it easier to discuss <img src='http://www.udidahan.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

