<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.outsightinteractive.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Outsight Interactive - Software Development Lessons Learned from Go - Comments</title>
 <link>http://www.outsightinteractive.com/blog/software_development_lessons_learned_from_go</link>
 <description>Comments for &quot;Software Development Lessons Learned from Go&quot;</description>
 <language>en</language>
<item>
 <title>Do you think this is what</title>
 <link>http://www.outsightinteractive.com/blog/software_development_lessons_learned_from_go#comment-1776</link>
 <description>&lt;p&gt;Do you think this is what Sun Tzu was talking about, a board game?&lt;/p&gt;
&lt;p&gt;As a Westerner I can say I&#039;ve never heard of the game either, but I&#039;m keen to find an online version so I can start learning. Thanks for the heads up!&lt;/p&gt;
</description>
 <pubDate>Tue, 12 Aug 2008 11:20:11 -0400</pubDate>
 <dc:creator>ffxi gil</dc:creator>
 <guid isPermaLink="false">comment 1776 at http://www.outsightinteractive.com</guid>
</item>
<item>
 <title>a bad start for the article.</title>
 <link>http://www.outsightinteractive.com/blog/software_development_lessons_learned_from_go#comment-672</link>
 <description>&lt;p&gt;a bad start for the article. go is not a game of territory, it is a game of fight, blood and flesh. it may happen that territory will be counted if no player has been exterminated. however, i enjoyed the proverb about the fist. really nice. and true :)&lt;/p&gt;
</description>
 <pubDate>Wed, 02 May 2007 17:20:29 -0400</pubDate>
 <dc:creator>Marc3</dc:creator>
 <guid isPermaLink="false">comment 672 at http://www.outsightinteractive.com</guid>
</item>
<item>
 <title>You are so right. I thought</title>
 <link>http://www.outsightinteractive.com/blog/software_development_lessons_learned_from_go#comment-644</link>
 <description>&lt;p&gt;You are so right. I thought that a martial arts metaphor might work. But now I see the light. I used to play a lot of go and I never saw the connection.&lt;/p&gt;
&lt;p&gt;Now that you&#039;ve pointed it out it&#039;s so clear. I&#039;m sure there&#039;s more wisdom that can be gleaned by extending the analogy and taking go wisdom and theory and applying it to coding.&lt;/p&gt;
&lt;p&gt;let&#039;s see there is fuseki, thickness, eyes, moyo, ... definitely something there.&lt;/p&gt;
</description>
 <pubDate>Sat, 21 Apr 2007 10:39:12 -0400</pubDate>
 <dc:creator>Choy</dc:creator>
 <guid isPermaLink="false">comment 644 at http://www.outsightinteractive.com</guid>
</item>
<item>
 <title>Thanks for stopping by. I&#039;m</title>
 <link>http://www.outsightinteractive.com/blog/software_development_lessons_learned_from_go#comment-641</link>
 <description>&lt;p&gt;Thanks for stopping by. I&#039;m glad you enjoyed the article.&lt;/p&gt;
&lt;p&gt;It&#039;s been a while since I&#039;ve done any functional programming (in Scheme, rather than LISP or Haskell), but I remember the overwhelming feeling of cleverness when figuring out just how to achieve something, and the overwhelming frustration when actually trying to implement it and discovering all of the gaps in my perception of the path to success. &lt;/p&gt;
&lt;p&gt;They&#039;re feelings very similar to discovering and then executing a clever Go move.&lt;/p&gt;
</description>
 <pubDate>Wed, 18 Apr 2007 14:19:50 -0400</pubDate>
 <dc:creator>Brandon</dc:creator>
 <guid isPermaLink="false">comment 641 at http://www.outsightinteractive.com</guid>
</item>
<item>
 <title>Excellent article!
I</title>
 <link>http://www.outsightinteractive.com/blog/software_development_lessons_learned_from_go#comment-640</link>
 <description>&lt;p&gt;Excellent article!&lt;/p&gt;
&lt;p&gt;I completely agree that the bizzare, yet structured, search space of Go closely resembles the search space that you access when programming. It is a far different feel than chess for example. I&#039;ll extend this analogy further and say that chess feels like programming in Java, because you have to memorizes huge libraries of moves/objects. Go feels more like Lisp or Haskell as you have to learn to create general structures that you fill in as needed. &lt;/p&gt;
&lt;p&gt;Good work! I like your group&#039;s blog. I&#039;ll add it to my loop.&lt;/p&gt;
</description>
 <pubDate>Wed, 18 Apr 2007 13:57:12 -0400</pubDate>
 <dc:creator>Entropyfails</dc:creator>
 <guid isPermaLink="false">comment 640 at http://www.outsightinteractive.com</guid>
</item>
<item>
 <title>Software Development Lessons Learned from Go</title>
 <link>http://www.outsightinteractive.com/blog/software_development_lessons_learned_from_go</link>
 <description>&lt;p&gt;&lt;span class=&quot;inline right&quot;&gt;&lt;img src=&quot;http://www.outsightinteractive.com/files/images/go2.jpg&quot; alt=&quot;The Game Go&quot; title=&quot;&quot; class=&quot;image img_assist_custom&quot; height=&quot;260&quot; width=&quot;200&quot;&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;The ancient board game Go is the most popular board game in the world, and yet few people in the United States have even heard of it. Go is a game of metaphors: it has been compared to &lt;em&gt;a fine art&lt;/em&gt;, &lt;em&gt;a martial art&lt;/em&gt;, &lt;em&gt;war&lt;/em&gt;, &lt;em&gt;a conversation&lt;/em&gt;, &lt;em&gt;life itself&lt;/em&gt;. Whereas Chess is a game of capturing prisoners, Go is a game of securing territory.&lt;/p&gt;
&lt;p&gt;At it&#039;s core the rules of Go are incredibly simple: Two players (Black and White) alternate in placing a single stone on a 19x19 grid. Touching stones of the same color form a unit, which can be captured if all of the unit&#039;s neighboring spaces in both the horizontal and vertical directions are occupied by opposing stones. Grid points which are completely surrounded by stones of a single color become territory for that player. The game ends when both players pass their turn (because further moves would be of no value). The winner is determined by adding the number of points of territory plus the number of prisoners taken for each player. You can check out the &lt;a href=&quot;http://www.usgo.org/resources/internet.html#Rules&quot;&gt; American Go Association&#039;s rules page&lt;/a&gt; for a more detailed discussion of the rules of go.&lt;/p&gt;
&lt;p&gt;Despite its simple rules, Go is at least PSPACE-hard, and could be as hard as EXPSPACE-complete, and the best Go programs consistently fail to perform much better than an experienced beginner. Though interesting, the computational complexity of the game of Go is not the purpose of this entry. What struck me, somewhere between the comment &quot;software projects are like many other things in the world, like many other things in the world.&quot; on &lt;a href=&quot;http://www.codinghorror.com/blog/archives/000830.html&quot;&gt; a recent entry by Jeff Atwood&lt;/a&gt;, and &lt;a href=&quot;http://tuxdeluxe.org/node/122&quot;&gt; a blip about &quot;writing code as art&quot;&lt;/a&gt; by Jeremy Allison, is that the game of Go, like many other things, has something to teach about software development.&lt;/p&gt;&lt;span class=&quot;readmore&quot;&gt;&lt;a href=&quot;/blog/software_development_lessons_learned_from_go&quot; title=&quot;Read more on this article&quot;&gt;read more...&lt;/a&gt;&lt;/span&gt;</description>
 <comments>http://www.outsightinteractive.com/blog/software_development_lessons_learned_from_go#comment</comments>
 <category domain="http://www.outsightinteractive.com/blog/tags/development">Development</category>
 <pubDate>Mon, 09 Apr 2007 14:47:31 -0400</pubDate>
 <dc:creator>Brandon</dc:creator>
 <guid isPermaLink="false">46 at http://www.outsightinteractive.com</guid>
</item>
</channel>
</rss>
