<?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: Udi Dahan: the biggest mistakes teams make when applying DDD</title>
	<atom:link href="http://gojko.net/2010/06/11/udi-dahan-the-biggest-mistakes-teams-make-when-applying-ddd/feed/" rel="self" type="application/rss+xml" />
	<link>http://gojko.net/2010/06/11/udi-dahan-the-biggest-mistakes-teams-make-when-applying-ddd/</link>
	<description>Building software that matters</description>
	<lastBuildDate>Fri, 18 May 2012 13:40:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Justin Forder</title>
		<link>http://gojko.net/2010/06/11/udi-dahan-the-biggest-mistakes-teams-make-when-applying-ddd/comment-page-1/#comment-91007</link>
		<dc:creator>Justin Forder</dc:creator>
		<pubDate>Fri, 18 Jun 2010 20:03:57 +0000</pubDate>
		<guid isPermaLink="false">http://gojko.net/?p=1876#comment-91007</guid>
		<description>Skills Matter now have the video and slides here: 

http://skillsmatter.com/podcast/design-architecture/architectural-innovation-cqrs/zx-553

This was a great talk; some of the mistakes were ones I recognised, and the others were thought-provoking... and the parts about CQRS led nicely in to Greg Young&#039;s talk.</description>
		<content:encoded><![CDATA[<p>Skills Matter now have the video and slides here: </p>
<p><a href="http://skillsmatter.com/podcast/design-architecture/architectural-innovation-cqrs/zx-553" rel="nofollow">http://skillsmatter.com/podcast/design-architecture/architectural-innovation-cqrs/zx-553</a></p>
<p>This was a great talk; some of the mistakes were ones I recognised, and the others were thought-provoking&#8230; and the parts about CQRS led nicely in to Greg Young&#8217;s talk.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DDD Exchange London 2010</title>
		<link>http://gojko.net/2010/06/11/udi-dahan-the-biggest-mistakes-teams-make-when-applying-ddd/comment-page-1/#comment-90131</link>
		<dc:creator>DDD Exchange London 2010</dc:creator>
		<pubDate>Sun, 13 Jun 2010 09:03:06 +0000</pubDate>
		<guid isPermaLink="false">http://gojko.net/?p=1876#comment-90131</guid>
		<description>[...] some time for Skills Matter to get the videos online so in the mean time I wanted to point you to Gojko blog post where he pretty much transcribed my talk word for [...]</description>
		<content:encoded><![CDATA[<p>[...] some time for Skills Matter to get the videos online so in the mean time I wanted to point you to Gojko blog post where he pretty much transcribed my talk word for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gustavo Melo</title>
		<link>http://gojko.net/2010/06/11/udi-dahan-the-biggest-mistakes-teams-make-when-applying-ddd/comment-page-1/#comment-89926</link>
		<dc:creator>Gustavo Melo</dc:creator>
		<pubDate>Fri, 11 Jun 2010 15:18:31 +0000</pubDate>
		<guid isPermaLink="false">http://gojko.net/?p=1876#comment-89926</guid>
		<description>Nice Post Gojko.

Udi make interesting points... this really make me think better !

I would like to talk about one thing:

&quot;Instead of solving race conditions with code, he suggested factoring time into design and talking to the business users about how the process was implemented before computers.&quot;

I understand that, but... 

We have evolved from paper to computer. It would&#039;t be correct build systems on their computers by changing the business logic according to evolution? What&#039;s wrong with changing the logic to worry about race conditions? The business logic should&#039;t evolve due to changes in technology?

Sry bad english...</description>
		<content:encoded><![CDATA[<p>Nice Post Gojko.</p>
<p>Udi make interesting points&#8230; this really make me think better !</p>
<p>I would like to talk about one thing:</p>
<p>&#8220;Instead of solving race conditions with code, he suggested factoring time into design and talking to the business users about how the process was implemented before computers.&#8221;</p>
<p>I understand that, but&#8230; </p>
<p>We have evolved from paper to computer. It would&#8217;t be correct build systems on their computers by changing the business logic according to evolution? What&#8217;s wrong with changing the logic to worry about race conditions? The business logic should&#8217;t evolve due to changes in technology?</p>
<p>Sry bad english&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

