<?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"
	>
<channel>
	<title>Comments on: How simple is too simple?</title>
	<atom:link href="http://dannorth.net/2006/05/how-simple-is-too-simple/feed" rel="self" type="application/rss+xml" />
	<link>http://dannorth.net/2006/05/how-simple-is-too-simple</link>
	<description>It's all behaviour</description>
	<pubDate>Sat, 11 Oct 2008 19:09:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Dan North</title>
		<link>http://dannorth.net/2006/05/how-simple-is-too-simple#comment-27</link>
		<dc:creator>Dan North</dc:creator>
		<pubDate>Sun, 04 Jun 2006 21:06:03 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/22#comment-27</guid>
		<description>That's an interesting observation. Before I got into mocking using jmock, I was also very wary of interfaces everywhere. Especially the dreaded Impl antipattern - the 1-1 mapping of CheeseService to CheeseServiceImpl. I've found that using TDD with mocks helps me "discover" services and dependencies that I mock using interfaces, so that I can defer worrying about the implementations until later. Tim Mackinnon - one of the originators of mock objects - describes these interfaces as "flex points". The interfaces that come out of mock-based TDD seem to appear just where I need multiple implementations down the line. Still not sure how, but I trust the mocking pixies and it seems to work.</description>
		<content:encoded><![CDATA[<p>That&#8217;s an interesting observation. Before I got into mocking using jmock, I was also very wary of interfaces everywhere. Especially the dreaded Impl antipattern &#8211; the 1-1 mapping of CheeseService to CheeseServiceImpl. I&#8217;ve found that using TDD with mocks helps me &#8220;discover&#8221; services and dependencies that I mock using interfaces, so that I can defer worrying about the implementations until later. Tim Mackinnon &#8211; one of the originators of mock objects &#8211; describes these interfaces as &#8220;flex points&#8221;. The interfaces that come out of mock-based TDD seem to appear just where I need multiple implementations down the line. Still not sure how, but I trust the mocking pixies and it seems to work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: del.icio.us bookmarks - 2006-06-03</title>
		<link>http://dannorth.net/2006/05/how-simple-is-too-simple#comment-26</link>
		<dc:creator>del.icio.us bookmarks - 2006-06-03</dc:creator>
		<pubDate>Sun, 04 Jun 2006 07:26:33 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/22#comment-26</guid>
		<description>[...] DanNorth.net » How simple is too simple? [...]</description>
		<content:encoded><![CDATA[<p>[...] DanNorth.net » How simple is too simple? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Baker</title>
		<link>http://dannorth.net/2006/05/how-simple-is-too-simple#comment-25</link>
		<dc:creator>Simon Baker</dc:creator>
		<pubDate>Sat, 03 Jun 2006 10:42:46 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/22#comment-25</guid>
		<description>Hi Dan,

Thanks for writing this interesting and thought provoking article. To hopefully put a face to a name, we met at ACCU this year. Syd introduced us. I previously worked with Syd before he joined Thoughtworks. I was at ACCU with Mauro Talevi and sat with him and joe Walnes in the Gumption Traps session.

Simon Baker.</description>
		<content:encoded><![CDATA[<p>Hi Dan,</p>
<p>Thanks for writing this interesting and thought provoking article. To hopefully put a face to a name, we met at ACCU this year. Syd introduced us. I previously worked with Syd before he joined Thoughtworks. I was at ACCU with Mauro Talevi and sat with him and joe Walnes in the Gumption Traps session.</p>
<p>Simon Baker.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Eckel</title>
		<link>http://dannorth.net/2006/05/how-simple-is-too-simple#comment-24</link>
		<dc:creator>Bruce Eckel</dc:creator>
		<pubDate>Thu, 01 Jun 2006 15:40:21 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/22#comment-24</guid>
		<description>"It does not discard using interfaces (almost) everywhere (*)"
Using interfaces everywhere is exactly the kind of "maybe we'll need this" thinking that DTSTTCPW is intended to eliminate.</description>
		<content:encoded><![CDATA[<p>&#8220;It does not discard using interfaces (almost) everywhere (*)&#8221;<br />
Using interfaces everywhere is exactly the kind of &#8220;maybe we&#8217;ll need this&#8221; thinking that DTSTTCPW is intended to eliminate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: de tomKronieken &#187; DanNorth.net » How simple is too simple?</title>
		<link>http://dannorth.net/2006/05/how-simple-is-too-simple#comment-23</link>
		<dc:creator>de tomKronieken &#187; DanNorth.net » How simple is too simple?</dc:creator>
		<pubDate>Thu, 01 Jun 2006 15:29:57 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/22#comment-23</guid>
		<description>[...] DanNorth.net » How simple is too simple? [...]</description>
		<content:encoded><![CDATA[<p>[...] DanNorth.net » How simple is too simple? [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
