<?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: Flowing Charts</title>
	<atom:link href="http://www.gameproducer.net/2010/08/19/flowing-charts/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gameproducer.net/2010/08/19/flowing-charts/</link>
	<description>I bake games. Indie style.</description>
	<lastBuildDate>Thu, 16 May 2013 13:23:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Lumooja</title>
		<link>http://www.gameproducer.net/2010/08/19/flowing-charts/comment-page-1/#comment-141815</link>
		<dc:creator>Lumooja</dc:creator>
		<pubDate>Fri, 20 Aug 2010 15:28:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.gameproducer.net/?p=5118#comment-141815</guid>
		<description>When you write a bit bigger software, then flowcharts will get a mess and you have no overview anymore.
With NSDs you can always make modular drawings, and although at the very first look you need to learn how they are read, they get very natural and easy to read on the 2nd look.
You can visually see immediately where you have loops and branches in your program.</description>
		<content:encoded><![CDATA[<p>When you write a bit bigger software, then flowcharts will get a mess and you have no overview anymore.<br />
With NSDs you can always make modular drawings, and although at the very first look you need to learn how they are read, they get very natural and easy to read on the 2nd look.<br />
You can visually see immediately where you have loops and branches in your program.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Iain</title>
		<link>http://www.gameproducer.net/2010/08/19/flowing-charts/comment-page-1/#comment-141814</link>
		<dc:creator>Iain</dc:creator>
		<pubDate>Fri, 20 Aug 2010 15:00:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.gameproducer.net/?p=5118#comment-141814</guid>
		<description>Ugh, at first glance that Nassi-Shneiderman diagram is very hard to follow.

I&#039;ve always used and seen bog standard flowcharts in real world development (i.e. not university and my own indie projects).

At the end of the day it&#039;s what suits you best I think.</description>
		<content:encoded><![CDATA[<p>Ugh, at first glance that Nassi-Shneiderman diagram is very hard to follow.</p>
<p>I&#8217;ve always used and seen bog standard flowcharts in real world development (i.e. not university and my own indie projects).</p>
<p>At the end of the day it&#8217;s what suits you best I think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: merc-ai</title>
		<link>http://www.gameproducer.net/2010/08/19/flowing-charts/comment-page-1/#comment-141811</link>
		<dc:creator>merc-ai</dc:creator>
		<pubDate>Fri, 20 Aug 2010 12:39:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.gameproducer.net/?p=5118#comment-141811</guid>
		<description>That&#039;s weird. We always used flowcharts for software documentation at university, and now I use it for some parts like when describing general game interface - all those option screens, save/load, new/quit etc.</description>
		<content:encoded><![CDATA[<p>That&#8217;s weird. We always used flowcharts for software documentation at university, and now I use it for some parts like when describing general game interface &#8211; all those option screens, save/load, new/quit etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lumooja</title>
		<link>http://www.gameproducer.net/2010/08/19/flowing-charts/comment-page-1/#comment-141807</link>
		<dc:creator>Lumooja</dc:creator>
		<pubDate>Fri, 20 Aug 2010 04:23:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.gameproducer.net/?p=5118#comment-141807</guid>
		<description>It&#039;s forbidden in universities to use flowcharts for software documentation. Nassi-Shneiderman diagram is the right tool for software documentation. It also prevents endless loops and illogical jumps.</description>
		<content:encoded><![CDATA[<p>It&#8217;s forbidden in universities to use flowcharts for software documentation. Nassi-Shneiderman diagram is the right tool for software documentation. It also prevents endless loops and illogical jumps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gustav Dahl / Wikzo</title>
		<link>http://www.gameproducer.net/2010/08/19/flowing-charts/comment-page-1/#comment-141800</link>
		<dc:creator>Gustav Dahl / Wikzo</dc:creator>
		<pubDate>Thu, 19 Aug 2010 17:56:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.gameproducer.net/?p=5118#comment-141800</guid>
		<description>What if you get stuck in a loop hole when reading your blog? Then you won&#039;t be able to break out of the site; you are trapped inside forever!</description>
		<content:encoded><![CDATA[<p>What if you get stuck in a loop hole when reading your blog? Then you won&#8217;t be able to break out of the site; you are trapped inside forever!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
