<?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: The dining geek problem</title>
	<atom:link href="http://www.metaprog.com/blogs/2009/06/the-dining-geek-problem/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.metaprog.com/blogs/2009/06/the-dining-geek-problem/</link>
	<description>Joseph Pelrine&#039;s weblog</description>
	<lastBuildDate>Mon, 03 Oct 2011 09:23:04 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: admin</title>
		<link>http://www.metaprog.com/blogs/2009/06/the-dining-geek-problem/comment-page-1/#comment-4</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 02 Jun 2009 11:05:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.metaprog.com/blogs/?p=55#comment-4</guid>
		<description>&lt;a href=&quot;#comment-3&quot; rel=&quot;nofollow&quot;&gt;@flowchainsensei&lt;/a&gt; 
Hi Bob,

Thanks for your comments. You do have a point here, although I get the feeling that &quot;themes&quot; would be yet another attractor/variable around which to self-organize, which would serve to increase, and not decrease the complexity of the situation. From another point of view, I see the things I considered - food, lodging, etc. - as more &quot;primary&quot; needs, and topics for intellectual discussion as more &quot;higher-order&quot; needs.

Cheers
Joseph</description>
		<content:encoded><![CDATA[<p><a href="#comment-3" rel="nofollow">@flowchainsensei</a><br />
Hi Bob,</p>
<p>Thanks for your comments. You do have a point here, although I get the feeling that &#8220;themes&#8221; would be yet another attractor/variable around which to self-organize, which would serve to increase, and not decrease the complexity of the situation. From another point of view, I see the things I considered &#8211; food, lodging, etc. &#8211; as more &#8220;primary&#8221; needs, and topics for intellectual discussion as more &#8220;higher-order&#8221; needs.</p>
<p>Cheers<br />
Joseph</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: flowchainsensei</title>
		<link>http://www.metaprog.com/blogs/2009/06/the-dining-geek-problem/comment-page-1/#comment-3</link>
		<dc:creator>flowchainsensei</dc:creator>
		<pubDate>Mon, 01 Jun 2009 15:27:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.metaprog.com/blogs/?p=55#comment-3</guid>
		<description>Hi Joseph,
As an attendee at you Open Space session on the Saturday, I was intrigued by your choice of the previous evening&#039;s events as a topic.

Although not party to the events of the Friday evening, when asking myself the questions you posed (and describe above), my own particular preference would have been to have discovered some &quot;themes&quot; for discussion, and to have organised around that. I realise that any one solution is unlikely to appeal to but a minority of the folks involved, but I&#039;d have been there (previous engagements otherwise permitting) to exchange ideas on certain specific topics of (hopefully) mutual interest.

Cheers
Bob</description>
		<content:encoded><![CDATA[<p>Hi Joseph,<br />
As an attendee at you Open Space session on the Saturday, I was intrigued by your choice of the previous evening&#8217;s events as a topic.</p>
<p>Although not party to the events of the Friday evening, when asking myself the questions you posed (and describe above), my own particular preference would have been to have discovered some &#8220;themes&#8221; for discussion, and to have organised around that. I realise that any one solution is unlikely to appeal to but a minority of the folks involved, but I&#8217;d have been there (previous engagements otherwise permitting) to exchange ideas on certain specific topics of (hopefully) mutual interest.</p>
<p>Cheers<br />
Bob</p>
]]></content:encoded>
	</item>
</channel>
</rss>

