<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (davidetarascibu)</title>
    <link>https://pinboard.in/u:davidetarascibu/public/</link>
    <description>recent bookmarks from davidetarascibu</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://37signals.com/svn/posts/3047-the-obvious-the-easy-and-the-possible"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://37signals.com/svn/posts/3047-the-obvious-the-easy-and-the-possible">
    <title>The Obvious, the Easy, and the Possible - (37signals)</title>
    <dc:date>2011-11-30T08:26:30+00:00</dc:date>
    <link>http://37signals.com/svn/posts/3047-the-obvious-the-easy-and-the-possible</link>
    <dc:creator>davidetarascibu</dc:creator><description><![CDATA[Shouldn’t everything be obvious? Unless you’re making a product that just does one thing – like a paperclip, for example – everything won’t be obvious. You have to make tough calls about what needs to be obvious, what should be easy, and what should be possible.]]></description>
<dc:subject>design development product sh</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:davidetarascibu/b:5490da146793/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:davidetarascibu/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:davidetarascibu/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:davidetarascibu/t:product"/>
	<rdf:li rdf:resource="https://pinboard.in/u:davidetarascibu/t:sh"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>