<?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: Design Dithering</title>
	<atom:link href="http://lostechies.com/colinramsay/2008/06/02/design-dithering/feed/" rel="self" type="application/rss+xml" />
	<link>http://lostechies.com/colinramsay/2008/06/02/design-dithering/</link>
	<description>Just another LosTechies site</description>
	<lastBuildDate>Wed, 27 May 2009 23:01:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Jeremy Wiebe</title>
		<link>http://lostechies.com/colinramsay/2008/06/02/design-dithering/#comment-54</link>
		<dc:creator>Jeremy Wiebe</dc:creator>
		<pubDate>Tue, 17 Jun 2008 00:19:30 +0000</pubDate>
		<guid isPermaLink="false">/blogs/colin_ramsay/archive/2008/06/02/design-dithering.aspx#comment-54</guid>
		<description>Man, you hit the nail on the head.  We&#039;re just starting out a new project and that has to be one of the hardest parts of a project.  What way do we access data?  How do we do localization?  An endless series of questions.  Today we all agreed to do a _thin_ vertical slice in our application and try to pull patterns we like/want out of that slice.  We know we&#039;ll miss some cross-cutting concerns we&#039;ll need, but we have to start somewhere and we figured that producing something in iteration 1 was better than a bunch of &quot;architecture&quot; that might miss the mark.   Wish us luck.  :-)  </description>
		<content:encoded><![CDATA[<p>Man, you hit the nail on the head.  We&#8217;re just starting out a new project and that has to be one of the hardest parts of a project.  What way do we access data?  How do we do localization?  An endless series of questions.  Today we all agreed to do a _thin_ vertical slice in our application and try to pull patterns we like/want out of that slice.  We know we&#8217;ll miss some cross-cutting concerns we&#8217;ll need, but we have to start somewhere and we figured that producing something in iteration 1 was better than a bunch of &#8220;architecture&#8221; that might miss the mark.   Wish us luck.  <img src='http://lostechies.com/colinramsay/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />   </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Evan</title>
		<link>http://lostechies.com/colinramsay/2008/06/02/design-dithering/#comment-53</link>
		<dc:creator>Evan</dc:creator>
		<pubDate>Tue, 03 Jun 2008 13:48:59 +0000</pubDate>
		<guid isPermaLink="false">/blogs/colin_ramsay/archive/2008/06/02/design-dithering.aspx#comment-53</guid>
		<description>I agree, and let me just add that there&#039;s no such thing as &quot;the correct way of implementing a shopping cart&quot;.  

Know what your end user needs and don&#039;t use tiering unless the project calls for it.  Many shopping carts will live happily as an asp.net website and a database.

If there&#039;s no driving reason for it, don&#039;t add complexity.  

Unless of course, you just have money and time to burn.  Then by all means, go ahead. :-)</description>
		<content:encoded><![CDATA[<p>I agree, and let me just add that there&#8217;s no such thing as &#8220;the correct way of implementing a shopping cart&#8221;.  </p>
<p>Know what your end user needs and don&#8217;t use tiering unless the project calls for it.  Many shopping carts will live happily as an asp.net website and a database.</p>
<p>If there&#8217;s no driving reason for it, don&#8217;t add complexity.  </p>
<p>Unless of course, you just have money and time to burn.  Then by all means, go ahead. <img src='http://lostechies.com/colinramsay/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cramsay</title>
		<link>http://lostechies.com/colinramsay/2008/06/02/design-dithering/#comment-52</link>
		<dc:creator>cramsay</dc:creator>
		<pubDate>Mon, 02 Jun 2008 20:03:26 +0000</pubDate>
		<guid isPermaLink="false">/blogs/colin_ramsay/archive/2008/06/02/design-dithering.aspx#comment-52</guid>
		<description>Totally. &quot;Pragmatic&quot; is the word which really encapsulates my post, because without pragmatism you&#039;re not going to meet your deadlines.</description>
		<content:encoded><![CDATA[<p>Totally. &#8220;Pragmatic&#8221; is the word which really encapsulates my post, because without pragmatism you&#8217;re not going to meet your deadlines.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Meridth</title>
		<link>http://lostechies.com/colinramsay/2008/06/02/design-dithering/#comment-51</link>
		<dc:creator>Jason Meridth</dc:creator>
		<pubDate>Mon, 02 Jun 2008 19:46:23 +0000</pubDate>
		<guid isPermaLink="false">/blogs/colin_ramsay/archive/2008/06/02/design-dithering.aspx#comment-51</guid>
		<description>Excellent advice.

Like the pragmatic guys say, KISS - &quot;Keep it simple stupid&quot;</description>
		<content:encoded><![CDATA[<p>Excellent advice.</p>
<p>Like the pragmatic guys say, KISS &#8211; &#8220;Keep it simple stupid&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
