<?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: SD East 2006 Day 1</title>
	<atom:link href="https://blackbeanbag.net/wp/2006/09/11/sd-east-2006-day-1/feed/" rel="self" type="application/rss+xml" />
	<link>https://blackbeanbag.net/wp/2006/09/11/sd-east-2006-day-1/</link>
	<description>Thoughts on software development and other stuff</description>
	<lastBuildDate>Sat, 20 Jul 2013 01:54:41 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=3.9.40</generator>
	<item>
		<title>By: pperalta [Member]</title>
		<link>https://blackbeanbag.net/wp/2006/09/11/sd-east-2006-day-1/comment-page-1/#comment-13</link>
		<dc:creator><![CDATA[pperalta [Member]]]></dc:creator>
		<pubDate>Thu, 14 Sep 2006 03:36:04 +0000</pubDate>
		<guid isPermaLink="false">http://blackbeanbag.net/wp/?p=24#comment-13</guid>
		<description><![CDATA[The cards on the wall were from the Spider Web (http://www.enthiosys.com/igspiderweb.php) game.  In this case, the spider web was about home PCs and what we use them for, what kind of peripherals we use with them, etc.  Half of the group acted as customers and drew up &quot;webs&quot; based on their own experiences with home PCs.  The other half played the role of vendor observer and wrote their observations on index cards.  The picture was taken while the cards were being arranged in order to determine what people were doing with their PCs and therefore what kinds of products or services would be useful to them.
]]></description>
		<content:encoded><![CDATA[<p>The cards on the wall were from the Spider Web (<a href="http://www.enthiosys.com/igspiderweb.php" rel="nofollow">http://www.enthiosys.com/igspiderweb.php</a>) game.  In this case, the spider web was about home PCs and what we use them for, what kind of peripherals we use with them, etc.  Half of the group acted as customers and drew up &#8220;webs&#8221; based on their own experiences with home PCs.  The other half played the role of vendor observer and wrote their observations on index cards.  The picture was taken while the cards were being arranged in order to determine what people were doing with their PCs and therefore what kinds of products or services would be useful to them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Moore [Visitor]</title>
		<link>https://blackbeanbag.net/wp/2006/09/11/sd-east-2006-day-1/comment-page-1/#comment-12</link>
		<dc:creator><![CDATA[Jim Moore [Visitor]]]></dc:creator>
		<pubDate>Wed, 13 Sep 2006 22:05:40 +0000</pubDate>
		<guid isPermaLink="false">http://blackbeanbag.net/wp/?p=24#comment-12</guid>
		<description><![CDATA[Very likely one of the major reasons that Martin didn&#039;t spend much time on interfaces is that it&#039;s an artifact of Java&#039;s implementation.  With TDD the &quot;declarative&quot; advantage is largely gone.  The only real advantage it gives is if you&#039;re using something like Spring, and then it&#039;s mostly in order to support proxying.  In other languages, like Ruby, virtually everything is an implementation and it&#039;s at least as easy to do loose coupling in Ruby as in Java.  &quot;interfaces&quot; in Java have a very specific static typing meaning, which is different than what you normally think of as an API interface.&lt;br /&gt;
&lt;br /&gt;
With those cards on the wall in the pics -- are they doing Open Spaces?
]]></description>
		<content:encoded><![CDATA[<p>Very likely one of the major reasons that Martin didn&#8217;t spend much time on interfaces is that it&#8217;s an artifact of Java&#8217;s implementation.  With TDD the &#8220;declarative&#8221; advantage is largely gone.  The only real advantage it gives is if you&#8217;re using something like Spring, and then it&#8217;s mostly in order to support proxying.  In other languages, like Ruby, virtually everything is an implementation and it&#8217;s at least as easy to do loose coupling in Ruby as in Java.  &#8220;interfaces&#8221; in Java have a very specific static typing meaning, which is different than what you normally think of as an API interface.</p>
<p>With those cards on the wall in the pics &#8212; are they doing Open Spaces?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
