<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Boxes and Arrows: Comments by Skot Nelson</title>
    <link>http://www.boxesandarrows.com/person/2864</link>
    <pubDate>Thu, 15 Mar 2007 17:00:49 GMT</pubDate>
    <description>Comments by Skot Nelson</description>
    <item>
      <description>&lt;p&gt;I think this is a great idea for an article. One thing is that the three points you&amp;#8217;ve mentioned above seeme to be focused ont the process or writing documentation, not the *importance* of writing documentation, which is what you&amp;#8217;re suggesting (at least by my reading of it.)&lt;/p&gt;

	&lt;p&gt;Were you going to look at it from the perspective of users?&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/idea/view/4050#content_5269</link>
      <guid>http://www.boxesandarrows.com/idea/view/4050#content_5269</guid>
      <pubDate>Thu, 15 Mar 2007 17:00:49 GMT</pubDate>
      <author>Skot Nelson</author>
    </item>
    <item>
      <description>&lt;p&gt;Presentation is a good start.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/idea/view/3592#content_5271</link>
      <guid>http://www.boxesandarrows.com/idea/view/3592#content_5271</guid>
      <pubDate>Tue, 06 Mar 2007 05:56:40 GMT</pubDate>
      <author>Skot Nelson</author>
    </item>
  </channel>
</rss>

