<?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: Identifying services we might need in the future but don&#8217;t know right now?</title>
	<atom:link href="http://sanderhoogendoorn.com/blog/?feed=rss2&#038;p=715" rel="self" type="application/rss+xml" />
	<link>http://sanderhoogendoorn.com/blog/?p=715</link>
	<description>Imagination is more important than knowledge</description>
	<lastBuildDate>Thu, 24 Jun 2010 15:16:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Marco</title>
		<link>http://sanderhoogendoorn.com/blog/?p=715&#038;cpage=1#comment-3096</link>
		<dc:creator>Marco</dc:creator>
		<pubDate>Fri, 27 Nov 2009 23:41:37 +0000</pubDate>
		<guid isPermaLink="false">http://sanderhoogendoorn.com/blog/?p=715#comment-3096</guid>
		<description>It took me a moment to realize what YAGNI means. For those of you who don&#039;t: &lt;a href=&quot;http://en.wikipedia.org/wiki/You_ain&#039;t_gonna_need_it&quot; target=&quot;_blank&quot;&gt;http://en.wikipedia.org/wiki/You_ain&#039;t_gonna...&lt;/a&gt; 
 
I completely agree with you. I have met my share of architects designing for some distant future. And I can&#039;t think of one single project based on these designs that worked out for the way it was envisoined. 
 
 </description>
		<content:encoded><![CDATA[<p>It took me a moment to realize what YAGNI means. For those of you who don&#039;t: <a href="http://en.wikipedia.org/wiki/You_ain&#039;t_gonna_need_it" target="_blank"></a><a href="http://en.wikipedia.org/wiki/You_ain&#039;t_gonna.." rel="nofollow">http://en.wikipedia.org/wiki/You_ain&#039;t_gonna..</a>. </p>
<p>I completely agree with you. I have met my share of architects designing for some distant future. And I can&#039;t think of one single project based on these designs that worked out for the way it was envisoined.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angelo Hulshout</title>
		<link>http://sanderhoogendoorn.com/blog/?p=715&#038;cpage=1#comment-3095</link>
		<dc:creator>Angelo Hulshout</dc:creator>
		<pubDate>Fri, 27 Nov 2009 19:16:24 +0000</pubDate>
		<guid isPermaLink="false">http://sanderhoogendoorn.com/blog/?p=715#comment-3095</guid>
		<description>Sander, it&#039;s getting crowded in the twilight zone.... I agree completely with what you write above. The point that a lot of [enterprise&#124;IT&#124;software] architects seem to miss is that being future proof is not the same as predicting the future. I won&#039;t go into repeating the ideas of frameworks, well defined interfaces, and extensible DSLs, but these are all ways to accomplish future proofness up to a certain level, without trying to predict all the services yagn.  
 
 
 
 </description>
		<content:encoded><![CDATA[<p>Sander, it&#039;s getting crowded in the twilight zone&#8230;. I agree completely with what you write above. The point that a lot of [enterprise|IT|software] architects seem to miss is that being future proof is not the same as predicting the future. I won&#039;t go into repeating the ideas of frameworks, well defined interfaces, and extensible DSLs, but these are all ways to accomplish future proofness up to a certain level, without trying to predict all the services yagn.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
