<?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: When is open source and standardization right?</title>
	<atom:link href="http://www.markedgington.com/2009/03/12/when-is-open-source-and-standardization-right/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markedgington.com/2009/03/12/when-is-open-source-and-standardization-right/</link>
	<description>news, views and reviews</description>
	<lastBuildDate>Wed, 18 Jan 2012 17:53:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Blogposts about QCon London 2009 &#124; JAOO Community Blog</title>
		<link>http://www.markedgington.com/2009/03/12/when-is-open-source-and-standardization-right/comment-page-1/#comment-96</link>
		<dc:creator>Blogposts about QCon London 2009 &#124; JAOO Community Blog</dc:creator>
		<pubDate>Mon, 30 Mar 2009 13:52:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.markedgington.com/?p=454#comment-96</guid>
		<description>[...] http://www.markedgington.com/2009/03/12/the-evolving-guardiancouk-architecture/ http://www.markedgington.com/2009/03/12/when-is-open-source-and-standardization-right/ http://www.markedgington.com/2009/03/13/a-story-about-a-technical-architect-pimp-my-architecture/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.markedgington.com/2009/03/12/the-evolving-guardiancouk-architecture/" rel="nofollow">http://www.markedgington.com/2009/03/12/the-evolving-guardiancouk-architecture/</a> <a href="http://www.markedgington.com/2009/03/12/when-is-open-source-and-standardization-right/" rel="nofollow">http://www.markedgington.com/2009/03/12/when-is-open-source-and-standardization-right/</a> <a href="http://www.markedgington.com/2009/03/13/a-story-about-a-technical-architect-pimp-my-architecture/" rel="nofollow">http://www.markedgington.com/2009/03/13/a-story-about-a-technical-architect-pimp-my-architecture/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kief</title>
		<link>http://www.markedgington.com/2009/03/12/when-is-open-source-and-standardization-right/comment-page-1/#comment-97</link>
		<dc:creator>Kief</dc:creator>
		<pubDate>Fri, 13 Mar 2009 06:56:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.markedgington.com/?p=454#comment-97</guid>
		<description>Standards should follow practice. EJB is the perfect example of defining standards for things like object persistence before the industry had actually worked out the best ways to do it. So the pre-maturely standardized persistence beans were a disaster, and Hibernate emerged as a decent model.There is a great story (I can&#039;t find via Google) about two different approaches to design. Imagine you have a corporate campus, and are trying to decide where to put paved footpaths between buildings. The normal approach is to do this before you build the campus. You can tell when a campus has been designed this way, because nobody uses the footpaths and you can see dirt paths people have worn into the grass.The second approach is to build the campus, but don&#039;t put the paths in at first. Wait until dirt paths emerge in the grass as people walk between buildings over the first few weeks, then pave those paths.</description>
		<content:encoded><![CDATA[<p>Standards should follow practice. EJB is the perfect example of defining standards for things like object persistence before the industry had actually worked out the best ways to do it. So the pre-maturely standardized persistence beans were a disaster, and Hibernate emerged as a decent model.</p>
<p>There is a great story (I can&#8217;t find via Google) about two different approaches to design. Imagine you have a corporate campus, and are trying to decide where to put paved footpaths between buildings. The normal approach is to do this before you build the campus. You can tell when a campus has been designed this way, because nobody uses the footpaths and you can see dirt paths people have worn into the grass.</p>
<p>The second approach is to build the campus, but don&#8217;t put the paths in at first. Wait until dirt paths emerge in the grass as people walk between buildings over the first few weeks, then pave those paths.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

