<?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 6 Reasons Your Game Development Tools Suck</title>
	<atom:link href="http://thetoolsmiths.org/2009/01/27/the-6-reasons-your-game-development-tools-suck/feed/" rel="self" type="application/rss+xml" />
	<link>http://thetoolsmiths.org/2009/01/27/the-6-reasons-your-game-development-tools-suck/</link>
	<description></description>
	<lastBuildDate>Tue, 27 Jul 2010 02:46:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Paul Evans</title>
		<link>http://thetoolsmiths.org/2009/01/27/the-6-reasons-your-game-development-tools-suck/comment-page-1/#comment-881</link>
		<dc:creator>Paul Evans</dc:creator>
		<pubDate>Wed, 26 May 2010 20:59:48 +0000</pubDate>
		<guid isPermaLink="false">http://toolssig.wordpress.com/?p=26#comment-881</guid>
		<description>Great article :-)</description>
		<content:encoded><![CDATA[<p>Great article <img src='http://thetoolsmiths.org/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reason 1 of 6 &#8211; Design As You Go &#171; The Toolsmiths</title>
		<link>http://thetoolsmiths.org/2009/01/27/the-6-reasons-your-game-development-tools-suck/comment-page-1/#comment-281</link>
		<dc:creator>Reason 1 of 6 &#8211; Design As You Go &#171; The Toolsmiths</dc:creator>
		<pubDate>Mon, 24 Aug 2009 13:38:10 +0000</pubDate>
		<guid isPermaLink="false">http://toolssig.wordpress.com/?p=26#comment-281</guid>
		<description>[...] Programming and Tool Design       This ongoing series delves more deeply into each of the &#8220;six reasons your game development tools suck&#8221; as argued in my very first [...]</description>
		<content:encoded><![CDATA[<p>[...] Programming and Tool Design       This ongoing series delves more deeply into each of the &#8220;six reasons your game development tools suck&#8221; as argued in my very first [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Problem With Ad-Hoc Tools Teams &#171; The Toolsmiths</title>
		<link>http://thetoolsmiths.org/2009/01/27/the-6-reasons-your-game-development-tools-suck/comment-page-1/#comment-280</link>
		<dc:creator>The Problem With Ad-Hoc Tools Teams &#171; The Toolsmiths</dc:creator>
		<pubDate>Tue, 03 Feb 2009 23:19:12 +0000</pubDate>
		<guid isPermaLink="false">http://toolssig.wordpress.com/?p=26#comment-280</guid>
		<description>[...] tools teams cause many problems, which, in some cases, form the groundwork for the 6 reasons Dan posted earlier. So, how does this happen, and what problems does it [...]</description>
		<content:encoded><![CDATA[<p>[...] tools teams cause many problems, which, in some cases, form the groundwork for the 6 reasons Dan posted earlier. So, how does this happen, and what problems does it [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik</title>
		<link>http://thetoolsmiths.org/2009/01/27/the-6-reasons-your-game-development-tools-suck/comment-page-1/#comment-279</link>
		<dc:creator>Erik</dc:creator>
		<pubDate>Wed, 28 Jan 2009 15:50:23 +0000</pubDate>
		<guid isPermaLink="false">http://toolssig.wordpress.com/?p=26#comment-279</guid>
		<description>I would add a 7th reason (though it arguably could come in under number 4).

7.  Not enough dogfooding
Often, the people who develop the tools don&#039;t actually use them.  This can lead to a number of problems, including an overly complex interface and a host of usability issues.

Overall remember that doing cool stuff should be easy, and doing wrong things should be hard.  The people using these tools are making your game cool.  They should spend time adding cool, not wrestling with adding cool.</description>
		<content:encoded><![CDATA[<p>I would add a 7th reason (though it arguably could come in under number 4).</p>
<p>7.  Not enough dogfooding<br />
Often, the people who develop the tools don&#8217;t actually use them.  This can lead to a number of problems, including an overly complex interface and a host of usability issues.</p>
<p>Overall remember that doing cool stuff should be easy, and doing wrong things should be hard.  The people using these tools are making your game cool.  They should spend time adding cool, not wrestling with adding cool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Ward</title>
		<link>http://thetoolsmiths.org/2009/01/27/the-6-reasons-your-game-development-tools-suck/comment-page-1/#comment-278</link>
		<dc:creator>Jeff Ward</dc:creator>
		<pubDate>Wed, 28 Jan 2009 15:46:42 +0000</pubDate>
		<guid isPermaLink="false">http://toolssig.wordpress.com/?p=26#comment-278</guid>
		<description>I think a lot of this stems from a &quot;one off&quot; approach to tools development.  Many programmers make what they think will be a tool just to make their own lives easier and one of two things happens: 1) It&#039;s useful and others start to use it when it&#039;s really not ready, or 2) Other programmers rework the problem because they don&#039;t know the tool exists.

I&#039;ve got a post about this brewing, so you&#039;ll see my full thoughts in the future.</description>
		<content:encoded><![CDATA[<p>I think a lot of this stems from a &#8220;one off&#8221; approach to tools development.  Many programmers make what they think will be a tool just to make their own lives easier and one of two things happens: 1) It&#8217;s useful and others start to use it when it&#8217;s really not ready, or 2) Other programmers rework the problem because they don&#8217;t know the tool exists.</p>
<p>I&#8217;ve got a post about this brewing, so you&#8217;ll see my full thoughts in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reavenk</title>
		<link>http://thetoolsmiths.org/2009/01/27/the-6-reasons-your-game-development-tools-suck/comment-page-1/#comment-277</link>
		<dc:creator>Reavenk</dc:creator>
		<pubDate>Wed, 28 Jan 2009 13:56:28 +0000</pubDate>
		<guid isPermaLink="false">http://toolssig.wordpress.com/?p=26#comment-277</guid>
		<description>I&#039;m working on in-house software that&#039;s not being used for games - and sadly, we still stuffer from all of these afflictions (except #2). I can definitly relate to this article.</description>
		<content:encoded><![CDATA[<p>I&#8217;m working on in-house software that&#8217;s not being used for games &#8211; and sadly, we still stuffer from all of these afflictions (except #2). I can definitly relate to this article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Munro</title>
		<link>http://thetoolsmiths.org/2009/01/27/the-6-reasons-your-game-development-tools-suck/comment-page-1/#comment-276</link>
		<dc:creator>James Munro</dc:creator>
		<pubDate>Wed, 28 Jan 2009 11:59:50 +0000</pubDate>
		<guid isPermaLink="false">http://toolssig.wordpress.com/?p=26#comment-276</guid>
		<description>These are interesting points. I&#039;m completing the final year of my games programming degree and I am interested on working as a tools designer/developer in the games industry, I will certainly take note of this advice.</description>
		<content:encoded><![CDATA[<p>These are interesting points. I&#8217;m completing the final year of my games programming degree and I am interested on working as a tools designer/developer in the games industry, I will certainly take note of this advice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony Brien</title>
		<link>http://thetoolsmiths.org/2009/01/27/the-6-reasons-your-game-development-tools-suck/comment-page-1/#comment-275</link>
		<dc:creator>Anthony Brien</dc:creator>
		<pubDate>Tue, 27 Jan 2009 23:49:03 +0000</pubDate>
		<guid isPermaLink="false">http://toolssig.wordpress.com/?p=26#comment-275</guid>
		<description>Oh, I&#039;m gonna like this new site :) Great post!

I agree with everything. From my experience, tools programmer are usually only given time to design the tools in the first months of a project. Afterwards, we only have time to fix/patch the tools. Then when the next project comes along (using the same pipeline and tools), the patching has embedded itself so deep in the code, its often easier to start over from scratch.</description>
		<content:encoded><![CDATA[<p>Oh, I&#8217;m gonna like this new site <img src='http://thetoolsmiths.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  Great post!</p>
<p>I agree with everything. From my experience, tools programmer are usually only given time to design the tools in the first months of a project. Afterwards, we only have time to fix/patch the tools. Then when the next project comes along (using the same pipeline and tools), the patching has embedded itself so deep in the code, its often easier to start over from scratch.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
