<?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: How to Design a Good API and Why it Matters</title>
	<atom:link href="http://www.techpresentations.com/2006/08/31/how-to-design-a-good-api-and-why-it-matters-by-joshua-bloch-google-inc/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.techpresentations.com/2006/08/31/how-to-design-a-good-api-and-why-it-matters-by-joshua-bloch-google-inc/</link>
	<description>Blog about technical presentations, mostly related to web</description>
	<pubDate>Fri, 21 Nov 2008 18:09:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-almost-beta-9300</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dr Simon Raybould</title>
		<link>http://www.techpresentations.com/2006/08/31/how-to-design-a-good-api-and-why-it-matters-by-joshua-bloch-google-inc/comment-page-1/#comment-19</link>
		<dc:creator>Dr Simon Raybould</dc:creator>
		<pubDate>Fri, 13 Oct 2006 21:04:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.techpresentations.com/2006/08/31/how-to-design-a-good-api-and-why-it-matters-by-joshua-bloch-google-inc/#comment-19</guid>
		<description>I'm no geek so I couldn't follow this presentation but I do work in the UK in &lt;a href="http://www.curved-vision.co.uk" rel="nofollow"&gt;presentation skills training&lt;/a&gt;, so I was interested in the presentation itself.

It's good.  Okay, it's too long and it uses far too many bullet-points so that I'll bet at least some of the audience lost the will to live before the end, but those  are minor crimes compared to the two big things it had going for it.

Firstly, the passion for the subject showed!

Secondly... almost more importantly.... the structure was flagged up for me almost all the time: as a reader (listener) I knew where I was in the presentation.  Even though I didn't understand the individual points on the slides, I understood what each slide was doing.  That's great, because if a non-specialist like me can do that, people in a specialist audience, who do understand the jargon, are going to be able to concentrate on the *content* rather than the *structure*.

That means understanding and retention both to up.

Big plus points to the author: if only more technical presentations were written this way!</description>
		<content:encoded><![CDATA[<p>I&#8217;m no geek so I couldn&#8217;t follow this presentation but I do work in the UK in <a href="http://www.curved-vision.co.uk" rel="nofollow">presentation skills training</a>, so I was interested in the presentation itself.</p>
<p>It&#8217;s good.  Okay, it&#8217;s too long and it uses far too many bullet-points so that I&#8217;ll bet at least some of the audience lost the will to live before the end, but those  are minor crimes compared to the two big things it had going for it.</p>
<p>Firstly, the passion for the subject showed!</p>
<p>Secondly&#8230; almost more importantly&#8230;. the structure was flagged up for me almost all the time: as a reader (listener) I knew where I was in the presentation.  Even though I didn&#8217;t understand the individual points on the slides, I understood what each slide was doing.  That&#8217;s great, because if a non-specialist like me can do that, people in a specialist audience, who do understand the jargon, are going to be able to concentrate on the *content* rather than the *structure*.</p>
<p>That means understanding and retention both to up.</p>
<p>Big plus points to the author: if only more technical presentations were written this way!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
