<?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: Usability-driven development</title>
	<atom:link href="http://cakebaker.42dh.com/2007/07/07/usability-driven-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://cakebaker.42dh.com/2007/07/07/usability-driven-development/</link>
	<description>baking cakes with CakePHP</description>
	<lastBuildDate>Sat, 13 Mar 2010 15:19:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: cakebaker</title>
		<link>http://cakebaker.42dh.com/2007/07/07/usability-driven-development/comment-page-1/#comment-7623</link>
		<dc:creator>cakebaker</dc:creator>
		<pubDate>Wed, 11 Jul 2007 06:53:09 +0000</pubDate>
		<guid isPermaLink="false">http://cakebaker.42dh.com/2007/07/07/usability-driven-development/#comment-7623</guid>
		<description>@Leif: I didn&#039;t include documentation because documentation is decoupled from the code. If I work with a component in my IDE, I have to leave the IDE to read the documentation. So documentation exists on its own. 

Personally I think a good user interface comes without any help menu and no tooltips. And so an undocumented API would be the ideal API we should aspire. I know, it sounds a bit illogical and like an idea of a lazy guy who doesn&#039;t want to document an API, but I think writing such an undocumented API requires more work if your goal is a good usability of the API. 

I agree with you that documentation is important, especially to provide the &quot;big picture&quot;, or in the form of tutorials.</description>
		<content:encoded><![CDATA[<p>@Leif: I didn&#8217;t include documentation because documentation is decoupled from the code. If I work with a component in my IDE, I have to leave the IDE to read the documentation. So documentation exists on its own. </p>
<p>Personally I think a good user interface comes without any help menu and no tooltips. And so an undocumented API would be the ideal API we should aspire. I know, it sounds a bit illogical and like an idea of a lazy guy who doesn&#8217;t want to document an API, but I think writing such an undocumented API requires more work if your goal is a good usability of the API. </p>
<p>I agree with you that documentation is important, especially to provide the &#8220;big picture&#8221;, or in the form of tutorials.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leif</title>
		<link>http://cakebaker.42dh.com/2007/07/07/usability-driven-development/comment-page-1/#comment-7608</link>
		<dc:creator>Leif</dc:creator>
		<pubDate>Mon, 09 Jul 2007 17:12:50 +0000</pubDate>
		<guid isPermaLink="false">http://cakebaker.42dh.com/2007/07/07/usability-driven-development/#comment-7608</guid>
		<description>Since you open your post with a reference to the &quot;no documentation&quot; post, I cannot keep my mouth shut. You claim &quot;[...] you can look at the public attributes and methods plus the comments as the user interface of a code component. [...]&quot; I couldn&#039;t agree more. But why do you exclude documentation when you include comments? Proper documentation is as good a part of good software as helpful comments are. An undocumented API is a user interface without any help menu and no tooltips. Documentation is a critical component of any software, be it for users or for programmers.</description>
		<content:encoded><![CDATA[<p>Since you open your post with a reference to the &#8220;no documentation&#8221; post, I cannot keep my mouth shut. You claim &#8220;[...] you can look at the public attributes and methods plus the comments as the user interface of a code component. [...]&#8221; I couldn&#8217;t agree more. But why do you exclude documentation when you include comments? Proper documentation is as good a part of good software as helpful comments are. An undocumented API is a user interface without any help menu and no tooltips. Documentation is a critical component of any software, be it for users or for programmers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoff Ford</title>
		<link>http://cakebaker.42dh.com/2007/07/07/usability-driven-development/comment-page-1/#comment-7596</link>
		<dc:creator>Geoff Ford</dc:creator>
		<pubDate>Sun, 08 Jul 2007 23:58:21 +0000</pubDate>
		<guid isPermaLink="false">http://cakebaker.42dh.com/2007/07/07/usability-driven-development/#comment-7596</guid>
		<description>I agree that a good, consistent  public interface is essential for a code component to be easily adopted.

I also think that bundled unit tests are great.  If I decide to hack something I like to know that it hasn&#039;t broken anything.</description>
		<content:encoded><![CDATA[<p>I agree that a good, consistent  public interface is essential for a code component to be easily adopted.</p>
<p>I also think that bundled unit tests are great.  If I decide to hack something I like to know that it hasn&#8217;t broken anything.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: othman ouahbi</title>
		<link>http://cakebaker.42dh.com/2007/07/07/usability-driven-development/comment-page-1/#comment-7595</link>
		<dc:creator>othman ouahbi</dc:creator>
		<pubDate>Sun, 08 Jul 2007 14:35:52 +0000</pubDate>
		<guid isPermaLink="false">http://cakebaker.42dh.com/2007/07/07/usability-driven-development/#comment-7595</guid>
		<description>Heh, I&#039;ve come to the same conclusion(s). the interface of code is very important, and not just for others, for yourself as well.</description>
		<content:encoded><![CDATA[<p>Heh, I&#8217;ve come to the same conclusion(s). the interface of code is very important, and not just for others, for yourself as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mito</title>
		<link>http://cakebaker.42dh.com/2007/07/07/usability-driven-development/comment-page-1/#comment-7592</link>
		<dc:creator>mito</dc:creator>
		<pubDate>Sat, 07 Jul 2007 19:41:59 +0000</pubDate>
		<guid isPermaLink="false">http://cakebaker.42dh.com/2007/07/07/usability-driven-development/#comment-7592</guid>
		<description>i definitely agree with u,
code should be written for its purpose, if it is component  its purpose is easy use for users (programmers)</description>
		<content:encoded><![CDATA[<p>i definitely agree with u,<br />
code should be written for its purpose, if it is component  its purpose is easy use for users (programmers)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
