<?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: Pimp my architecture &#8211; Dan North</title>
	<atom:link href="http://www.markhneedham.com/blog/2009/04/25/pimp-my-architecture-dan-north/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markhneedham.com/blog/2009/04/25/pimp-my-architecture-dan-north/</link>
	<description>Thoughts on Software Development</description>
	<lastBuildDate>Sat, 11 Feb 2012 23:17:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Learnings from my first project of 2010 at Mark Needham</title>
		<link>http://www.markhneedham.com/blog/2009/04/25/pimp-my-architecture-dan-north/comment-page-1/#comment-36438</link>
		<dc:creator>Learnings from my first project of 2010 at Mark Needham</dc:creator>
		<pubDate>Sun, 09 May 2010 22:19:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=1160#comment-36438</guid>
		<description>[...] arrived at through a series of steps which did make sense. Dan North talks of the need to have a project shaman who can tell the story of why certain decisions were made and the history behind them and it&#039;s [...]</description>
		<content:encoded><![CDATA[<p>[...] arrived at through a series of steps which did make sense. Dan North talks of the need to have a project shaman who can tell the story of why certain decisions were made and the history behind them and it&#39;s [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Book Club: Working Effectively With Legacy Code – Chapters 17, 18 and 19 (Michael Feathers) &#171; Liz Douglass</title>
		<link>http://www.markhneedham.com/blog/2009/04/25/pimp-my-architecture-dan-north/comment-page-1/#comment-28622</link>
		<dc:creator>Book Club: Working Effectively With Legacy Code – Chapters 17, 18 and 19 (Michael Feathers) &#171; Liz Douglass</dc:creator>
		<pubDate>Sat, 19 Dec 2009 07:28:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=1160#comment-28622</guid>
		<description>[...] I think this technique is related to Dan&#8217;s idea of having a project shaman. [...]</description>
		<content:encoded><![CDATA[<p>[...] I think this technique is related to Dan&#8217;s idea of having a project shaman. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Hunger</title>
		<link>http://www.markhneedham.com/blog/2009/04/25/pimp-my-architecture-dan-north/comment-page-1/#comment-15254</link>
		<dc:creator>Michael Hunger</dc:creator>
		<pubDate>Fri, 24 Apr 2009 20:11:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=1160#comment-15254</guid>
		<description>Thanks for the writeup Mark. I also enjoyed the talk very much and spoke a lot about it to colleguages and friends. Hopefully the infoq guys release the video not so late.

What I also found interesting was the allowance to try things out - not to get them right the first time. The example was refactoring to Command Pattern when it was an overkill.

Another thing is the ability to step back and recognize accidental complexity and to focus on getting the essential complexity of the problem covered without adding much overhead.

CU

Michael</description>
		<content:encoded><![CDATA[<p>Thanks for the writeup Mark. I also enjoyed the talk very much and spoke a lot about it to colleguages and friends. Hopefully the infoq guys release the video not so late.</p>
<p>What I also found interesting was the allowance to try things out &#8211; not to get them right the first time. The example was refactoring to Command Pattern when it was an overkill.</p>
<p>Another thing is the ability to step back and recognize accidental complexity and to focus on getting the essential complexity of the problem covered without adding much overhead.</p>
<p>CU</p>
<p>Michael</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arjan`s World &#187; LINKBLOG for April 24, 2009</title>
		<link>http://www.markhneedham.com/blog/2009/04/25/pimp-my-architecture-dan-north/comment-page-1/#comment-15251</link>
		<dc:creator>Arjan`s World &#187; LINKBLOG for April 24, 2009</dc:creator>
		<pubDate>Fri, 24 Apr 2009 19:45:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=1160#comment-15251</guid>
		<description>[...] Pimp my architecture - Dan North - Mark Needham Mark shares his lessons learned from a talk on &#8216;pimping your architecture&#8217; given by his collegue Dan North [...]</description>
		<content:encoded><![CDATA[<p>[...] Pimp my architecture &#8211; Dan North &#8211; Mark Needham Mark shares his lessons learned from a talk on &#8216;pimping your architecture&#8217; given by his collegue Dan North [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

