<?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: Reason 1 of 6 &#8211; Design As You Go</title>
	<atom:link href="http://thetoolsmiths.org/2009/08/24/reason-1-of-6-design-as-you-go/feed/" rel="self" type="application/rss+xml" />
	<link>http://thetoolsmiths.org/2009/08/24/reason-1-of-6-design-as-you-go/</link>
	<description></description>
	<lastBuildDate>Mon, 16 Aug 2010 17:08:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: David McGraw</title>
		<link>http://thetoolsmiths.org/2009/08/24/reason-1-of-6-design-as-you-go/comment-page-1/#comment-547</link>
		<dc:creator>David McGraw</dc:creator>
		<pubDate>Fri, 16 Oct 2009 05:43:25 +0000</pubDate>
		<guid isPermaLink="false">http://toolssig.wordpress.com/?p=336#comment-547</guid>
		<description>I&#039;m currently seeing this in action where I work at now (movie-animation studio).  Just busting in the door for the first time, it&#039;s amazing to see how little technical design effort goes toward tools development.  It&#039;s the nature of the beast.  Overcome, adapt, and iterate.</description>
		<content:encoded><![CDATA[<p>I&#8217;m currently seeing this in action where I work at now (movie-animation studio).  Just busting in the door for the first time, it&#8217;s amazing to see how little technical design effort goes toward tools development.  It&#8217;s the nature of the beast.  Overcome, adapt, and iterate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anders Elfgren</title>
		<link>http://thetoolsmiths.org/2009/08/24/reason-1-of-6-design-as-you-go/comment-page-1/#comment-516</link>
		<dc:creator>Anders Elfgren</dc:creator>
		<pubDate>Mon, 24 Aug 2009 20:52:19 +0000</pubDate>
		<guid isPermaLink="false">http://toolssig.wordpress.com/?p=336#comment-516</guid>
		<description>I agree with most of what you say. One way to solve is the way you imply (at least I think you do :) ), i.e. have the designers really design the tool first - then let the tools programmer follow the design as he or she implements it.

In my experience (three years of tools development at Avalanche Studios), it is VERY difficult to understand all the requirements of a tool before you start to use it, or even starting the implementation.

I wrote a full response here:
http://anderselfgren.blogspot.com/2009/08/tools-design-as-you-go.html</description>
		<content:encoded><![CDATA[<p>I agree with most of what you say. One way to solve is the way you imply (at least I think you do <img src='http://thetoolsmiths.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  ), i.e. have the designers really design the tool first &#8211; then let the tools programmer follow the design as he or she implements it.</p>
<p>In my experience (three years of tools development at Avalanche Studios), it is VERY difficult to understand all the requirements of a tool before you start to use it, or even starting the implementation.</p>
<p>I wrote a full response here:<br />
<a href="http://anderselfgren.blogspot.com/2009/08/tools-design-as-you-go.html" rel="nofollow">http://anderselfgren.blogspot.com/2009/08/tools-design-as-you-go.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
