<?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: The Big Ball of Mud</title>
	<atom:link href="http://topsecretproject.finitestatemachine.com/2009/03/the-big-ball-of-mud/feed/" rel="self" type="application/rss+xml" />
	<link>http://topsecretproject.finitestatemachine.com/2009/03/the-big-ball-of-mud/</link>
	<description>Ruby, Rails, Web Technology, Varied Miscellanea</description>
	<lastBuildDate>Wed, 03 Nov 2010 02:19:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: tim</title>
		<link>http://topsecretproject.finitestatemachine.com/2009/03/the-big-ball-of-mud/comment-page-1/#comment-4543</link>
		<dc:creator>tim</dc:creator>
		<pubDate>Fri, 21 May 2010 22:44:20 +0000</pubDate>
		<guid isPermaLink="false">http://topsecretproject.finitestatemachine.com/?p=25#comment-4543</guid>
		<description>thats a slippery slope though - if you build to a feature spec, you might loose sight of scalability.

I&#039;d actually propose you focus on structural base functinoality, but leave features for later, then build a base architecture that is abstract and truly object oriented.

and presto, you&#039;re on your way to great software.

except, doing things this way require investments in frameworks that aren&#039;t immediately visible by business owners, and thus rarely get funded. and so we go back to the old convoluted way of building software feature-by-feature, until it&#039;s a BIG BALL OF MUD.

...sigh...</description>
		<content:encoded><![CDATA[<p>thats a slippery slope though &#8211; if you build to a feature spec, you might loose sight of scalability.</p>
<p>I&#8217;d actually propose you focus on structural base functinoality, but leave features for later, then build a base architecture that is abstract and truly object oriented.</p>
<p>and presto, you&#8217;re on your way to great software.</p>
<p>except, doing things this way require investments in frameworks that aren&#8217;t immediately visible by business owners, and thus rarely get funded. and so we go back to the old convoluted way of building software feature-by-feature, until it&#8217;s a BIG BALL OF MUD.</p>
<p>&#8230;sigh&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nicholas f</title>
		<link>http://topsecretproject.finitestatemachine.com/2009/03/the-big-ball-of-mud/comment-page-1/#comment-2</link>
		<dc:creator>nicholas f</dc:creator>
		<pubDate>Tue, 10 Mar 2009 12:16:14 +0000</pubDate>
		<guid isPermaLink="false">http://topsecretproject.finitestatemachine.com/?p=25#comment-2</guid>
		<description>Definitely. In fact, sometimes following such principles and focusing on simplicity can end with very elegant pieces of code which &#039;do the job&#039;, rather than the grander preconceptions which a mind can build up with preconcceptions of design and architecture.</description>
		<content:encoded><![CDATA[<p>Definitely. In fact, sometimes following such principles and focusing on simplicity can end with very elegant pieces of code which &#8216;do the job&#8217;, rather than the grander preconceptions which a mind can build up with preconcceptions of design and architecture.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

