<?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: How a beautiful software system becomes Frankenstein</title>
	<atom:link href="http://softwarecreation.org/2008/how-a-beautiful-software-system-becomes-frankenstein/feed/" rel="self" type="application/rss+xml" />
	<link>http://softwarecreation.org/2008/how-a-beautiful-software-system-becomes-frankenstein/</link>
	<description>What are the forces behind software development?</description>
	<lastBuildDate>Fri, 03 Feb 2012 19:54:53 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Richard S</title>
		<link>http://softwarecreation.org/2008/how-a-beautiful-software-system-becomes-frankenstein/comment-page-1/#comment-18329</link>
		<dc:creator>Richard S</dc:creator>
		<pubDate>Fri, 16 Jan 2009 16:35:15 +0000</pubDate>
		<guid isPermaLink="false">http://softwarecreation.org/2008/how-a-beautiful-software-system-becomes-frankenstein/#comment-18329</guid>
		<description>Thanks for the great article, should be required reading for product owners/managers as well as developers.  I think the argument applies just as much to the product requirements as to the design.  So many times software is compromised by a lack of understanding or focus on the core functionality.  Unless that vision is right the best development will still give a compromised product.  I&#039;ve talked about that a bit in &lt;a href=&quot;http://blogs.oracle.com/socialcrm/2009/01/i_didnt_have_time_to_make_a_si.html&quot; rel=&quot;nofollow&quot;&gt;this blog entry&lt;/a&gt; if you&#039;re interested.</description>
		<content:encoded><![CDATA[<p>Thanks for the great article, should be required reading for product owners/managers as well as developers.  I think the argument applies just as much to the product requirements as to the design.  So many times software is compromised by a lack of understanding or focus on the core functionality.  Unless that vision is right the best development will still give a compromised product.  I&#8217;ve talked about that a bit in <a href="http://blogs.oracle.com/socialcrm/2009/01/i_didnt_have_time_to_make_a_si.html" rel="nofollow">this blog entry</a> if you&#8217;re interested.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LinkLog: Startups &#171; Dorai&#8217;s LearnLog</title>
		<link>http://softwarecreation.org/2008/how-a-beautiful-software-system-becomes-frankenstein/comment-page-1/#comment-2990</link>
		<dc:creator>LinkLog: Startups &#171; Dorai&#8217;s LearnLog</dc:creator>
		<pubDate>Sun, 02 Mar 2008 03:50:11 +0000</pubDate>
		<guid isPermaLink="false">http://softwarecreation.org/2008/how-a-beautiful-software-system-becomes-frankenstein/#comment-2990</guid>
		<description>[...] by Seth Godin&#8217;s Soggy.A similar abstraction, on a very different subject-  software. How a beautiful software system becomes Frankenstein paints a vivid picture of what happens when you grow from small to [...]</description>
		<content:encoded><![CDATA[<p>[...] by Seth Godin&#8217;s Soggy.A similar abstraction, on a very different subject-  software. How a beautiful software system becomes Frankenstein paints a vivid picture of what happens when you grow from small to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LinkLog: Software &#171; Dorai&#8217;s LearnLog</title>
		<link>http://softwarecreation.org/2008/how-a-beautiful-software-system-becomes-frankenstein/comment-page-1/#comment-2922</link>
		<dc:creator>LinkLog: Software &#171; Dorai&#8217;s LearnLog</dc:creator>
		<pubDate>Fri, 29 Feb 2008 05:30:17 +0000</pubDate>
		<guid isPermaLink="false">http://softwarecreation.org/2008/how-a-beautiful-software-system-becomes-frankenstein/#comment-2922</guid>
		<description>[...] How a beautiful idea becomes a Frankenstein system is a must read for every software developer.  Here is a small fragment of a much more comprehensive diagram in this post. [...]</description>
		<content:encoded><![CDATA[<p>[...] How a beautiful idea becomes a Frankenstein system is a must read for every software developer.  Here is a small fragment of a much more comprehensive diagram in this post. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How beautiful code becomes ugly&#8230;..fast &#124; Sexy Jihad</title>
		<link>http://softwarecreation.org/2008/how-a-beautiful-software-system-becomes-frankenstein/comment-page-1/#comment-2895</link>
		<dc:creator>How beautiful code becomes ugly&#8230;..fast &#124; Sexy Jihad</dc:creator>
		<pubDate>Thu, 28 Feb 2008 10:39:10 +0000</pubDate>
		<guid isPermaLink="false">http://softwarecreation.org/2008/how-a-beautiful-software-system-becomes-frankenstein/#comment-2895</guid>
		<description>[...] Well, enough ranting my readers (all 8 of you that visit my site daily at the moment). The good news is that Software Creation Mystery has written an article about just this phenomena: [...]</description>
		<content:encoded><![CDATA[<p>[...] Well, enough ranting my readers (all 8 of you that visit my site daily at the moment). The good news is that Software Creation Mystery has written an article about just this phenomena: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexey</title>
		<link>http://softwarecreation.org/2008/how-a-beautiful-software-system-becomes-frankenstein/comment-page-1/#comment-2865</link>
		<dc:creator>Alexey</dc:creator>
		<pubDate>Wed, 27 Feb 2008 15:00:43 +0000</pubDate>
		<guid isPermaLink="false">http://softwarecreation.org/2008/how-a-beautiful-software-system-becomes-frankenstein/#comment-2865</guid>
		<description>Wonderful article. Well structured and well thought, plenty of good advices for PM and team leads. I agree with most of statements I can reason about.</description>
		<content:encoded><![CDATA[<p>Wonderful article. Well structured and well thought, plenty of good advices for PM and team leads. I agree with most of statements I can reason about.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

