<?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: SRP: Single Responsibility Principle</title>
	<atom:link href="http://www.softwarerockstar.com/2006/08/srp-single-responsibility-principle/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.softwarerockstar.com/2006/08/srp-single-responsibility-principle/</link>
	<description>Coaching and mentoring on a journey from a Developer to an IT Leader</description>
	<lastBuildDate>Sat, 27 Aug 2011 18:39:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: google</title>
		<link>http://www.softwarerockstar.com/2006/08/srp-single-responsibility-principle/comment-page-1/#comment-4121</link>
		<dc:creator>google</dc:creator>
		<pubDate>Sat, 27 Aug 2011 18:39:15 +0000</pubDate>
		<guid isPermaLink="false">http://mharoon.wordpress.com/2006/08/20/srp-single-responsibility-principle/#comment-4121</guid>
		<description>I liked your article is an interesting technology 
thanks to google I found you</description>
		<content:encoded><![CDATA[<p>I liked your article is an interesting technology<br />
thanks to google I found you</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: M. Haroon</title>
		<link>http://www.softwarerockstar.com/2006/08/srp-single-responsibility-principle/comment-page-1/#comment-34</link>
		<dc:creator>M. Haroon</dc:creator>
		<pubDate>Tue, 13 Feb 2007 16:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://mharoon.wordpress.com/2006/08/20/srp-single-responsibility-principle/#comment-34</guid>
		<description>There is not really a silver bullet, if you will, and whether or not to apply this principle should be determined by the situation at hand.  There may be situations where extensibility is required, in which case separation of business logic from persistence logic shall be desirable; in other situations where, for example, you are guaranteed to always be persisting to a file in the same format, for example, separating these responsibilities may only introduce needless complexity.</description>
		<content:encoded><![CDATA[<p>There is not really a silver bullet, if you will, and whether or not to apply this principle should be determined by the situation at hand.  There may be situations where extensibility is required, in which case separation of business logic from persistence logic shall be desirable; in other situations where, for example, you are guaranteed to always be persisting to a file in the same format, for example, separating these responsibilities may only introduce needless complexity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonas</title>
		<link>http://www.softwarerockstar.com/2006/08/srp-single-responsibility-principle/comment-page-1/#comment-33</link>
		<dc:creator>Jonas</dc:creator>
		<pubDate>Tue, 13 Feb 2007 09:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://mharoon.wordpress.com/2006/08/20/srp-single-responsibility-principle/#comment-33</guid>
		<description>Well. I think that you should separate those two. Will you always save the information to a file? Will you always save it in the same format? I think not =)</description>
		<content:encoded><![CDATA[<p>Well. I think that you should separate those two. Will you always save the information to a file? Will you always save it in the same format? I think not =)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

