<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Geekish Stuff &#187; Google Tech Talks</title>
	<atom:link href="http://blog.braceta.com/category/google-tech-talks/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.braceta.com</link>
	<description>pun for geeks, stuff that doesn't matter</description>
	<lastBuildDate>Thu, 05 Jan 2012 22:32:05 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Another Review: How to Design a Good API and Why it Matters</title>
		<link>http://blog.braceta.com/another-review-how-to-design-a-good-api-and-why-it-matters/</link>
		<comments>http://blog.braceta.com/another-review-how-to-design-a-good-api-and-why-it-matters/#comments</comments>
		<pubDate>Sun, 09 Dec 2007 02:31:58 +0000</pubDate>
		<dc:creator>braceta</dc:creator>
				<category><![CDATA[Google Tech Talks]]></category>
		<category><![CDATA[Tech]]></category>

		<guid isPermaLink="false">http://blog.braceta.com/2007/12/09/another-review-how-to-design-a-good-api-and-why-it-matters/</guid>
		<description><![CDATA[How many of you tried to write a complete good API? Well, perhaps not so many. An API is only good if is intended to be used by others. But if you are a software engineer you must ensure if it will be used, you will invest your time doing it right from the start. [...]]]></description>
			<content:encoded><![CDATA[<p>How many of you tried to write a complete good API? Well, perhaps not so many.  An API is only good if is intended to be used by others. But if you are a software engineer you must ensure if it will be used, you will invest your time doing it right from the start.</p>
<p><a href="http://en.wikipedia.org/wiki/Joshua_Bloch">Joshua Bloch </a>gave a very interesting <a href="http://www.youtube.com/watch?v=aAb7hSCtvGw&amp;feature=related" target="_blank">talk</a> at Google focusing this subject. Some key points where highlighted to have in mind when designing a good API.</p>
<p>It was a nice talk, mainly because Joshua is a good orator therefore captures your attention trough the whole session. Nevertheless he haven&#8217;t got time to finish the talk skipping the two last chapters. Don&#8217;t ask me why but google seems strict when concerning to time session (maybe there&#8217;s no more tape to record? :) ).</p>
<p>Some key points to save from talk:</p>
<ul>
<li><strong>When doubt let it out:</strong> you can add it later;</li>
<li>Keep your API Specification short and simple;</li>
<li>Method and Class names are Important;</li>
<li> Fail fast: return errors as soon as possible</li>
</ul>
<p>I rate 4 stars of 5 for the importance of the subject. I only give 4 because the talk is not complete. Even tough you can infer the rest from the <a href="http://lcsd05.cs.tamu.edu/slides/keynote.pdf">slides</a>.</p>
<div id="simple_socialmedia"><ul class="ssm_row"><li class="twitter"><a target="_blank" href="http://twitter.com/share?url=http://blog.braceta.com/another-review-how-to-design-a-good-api-and-why-it-matters/&amp;text=Another Review: How to Design a Good API and Why it Matters&amp;via=braceta">Tweet</a></li><li class="facebook"><a target="_blank" title="Share on Facebook" rel="nofollow" href="http://www.facebook.com/sharer.php?u=http://blog.braceta.com/another-review-how-to-design-a-good-api-and-why-it-matters/&amp;t=Another Review: How to Design a Good API and Why it Matters">Facebook</a></li><li class="linkedin"><a target="_blank" title="Share on LinkedIn" rel="nofollow" href="http://www.linkedin.com/shareArticle?mini=true&amp;url=http://blog.braceta.com/another-review-how-to-design-a-good-api-and-why-it-matters/&amp;title=Another Review: How to Design a Good API and Why it Matters&amp;source=Geekish Stuff">LinkedIn</a></li><li class="tumblr"><a target="_blank" title="Share on Tumblr" rel="nofollow" href="http://www.tumblr.com/share/link?url=http%3A%2F%2Fblog.braceta.com%2Fanother-review-how-to-design-a-good-api-and-why-it-matters%2F&name=Geekish+Stuff&description=Another+Review%3A+How+to+Design+a+Good+API+and+Why+it+Matters" title="Share on Tumblr">Tumblr</a></li><li class="stumble"><a target="_blank" title="Share on StumbleUpon" rel="nofollow" href="http://www.stumbleupon.com/submit?url=http://blog.braceta.com/another-review-how-to-design-a-good-api-and-why-it-matters/">Stumble</a></li><li class="digg"><a target="_blank" title="Share on Digg" rel="nofollow" href="http://www.digg.com/submit?phase=2&amp;url=http://blog.braceta.com/another-review-how-to-design-a-good-api-and-why-it-matters/">Digg</a></li><li class="delicious"><a target="_blank" title="Share on Delicious" rel="nofollow" href="http://del.icio.us/post?url=http://blog.braceta.com/another-review-how-to-design-a-good-api-and-why-it-matters/&amp;title=INSERT_TITLE">Delicious</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>http://blog.braceta.com/another-review-how-to-design-a-good-api-and-why-it-matters/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

