<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/">

    <channel>
    
    <title>A Working Library: Reading</title>
    <link>http://www.aworkinglibrary.com/library/reading</link>
    <description></description>
    <dc:language>en</dc:language>
    <dc:creator>mandy@aworkinglibrary.com</dc:creator>
    <dc:rights>Copyright 2012</dc:rights>
    <dc:date>2012-03-26T13:25:35+00:00</dc:date>
    <admin:generatorAgent rdf:resource="http://expressionengine.com/" />
    

    <item>
      <title>Design Is a Job</title>
      <link>http://aworkinglibrary.com/feeder/?FeederAction=clicked&amp;feed=Reading&amp;seed=http%3A%2F%2Faworkinglibrary.com%2Flibrary%2Fbook%2Fdesign_is_a_job%2F&amp;seed_title=Design+Is+a+Job</link>
      <description><![CDATA[Mike Monteiro's writing is as ruthless as it is wise. A love letter to web designers everywhere, <em>Design Is a Job</em> catalogs the many and varied mistakes one can make on the path to being successful, and generously warns you away from them. The result is a book that is personal and profound, and which you'll be waving around to friends and colleagues before you even complete it.  "So I wrote you a book," Mike says. "It has a spine and by the time you're done reading <em>so will you</em>."<img src="http://www.aworkinglibrary.com/images/covers/monteiro-design-is-a-job.jpg" class="cover" alt="book_cover" width="320" height="495" /> ]]></description>
      <dc:subject>A Book Apart, Mike Monteiro</dc:subject>
      <dc:date>2012-04-10T14:58:43+00:00</dc:date>
    </item>

    <item>
      <title>Love, An Index</title>
      <link>http://aworkinglibrary.com/feeder/?FeederAction=clicked&amp;feed=Reading&amp;seed=http%3A%2F%2Faworkinglibrary.com%2Flibrary%2Fbook%2Flove_an_index%2F&amp;seed_title=Love%2C+An+Index</link>
      <description><![CDATA[When a friend publishes a book, it is cause for celebration. When the topic is the loss of the man she loved, the celebration is heartbreaking. Rebecca's words touch on darker days, but the form and style are extraordinary even if held apart from the event that triggered them. <img src="http://www.aworkinglibrary.com/images/covers/lindenberg-love-an-index.jpg" class="cover" alt="book_cover" width="320" height="440" /> ]]></description>
      <dc:subject>McSweeney&#39;s, Rebecca Lindenberg</dc:subject>
      <dc:date>2012-04-08T17:05:10+00:00</dc:date>
    </item>

    <item>
      <title>Robbed</title>
      <link>http://aworkinglibrary.com/feeder/?FeederAction=clicked&amp;feed=Reading&amp;seed=http%3A%2F%2Faworkinglibrary.com%2Flibrary%2Farchives%2Frobbed%2F&amp;seed_title=Robbed</link>
      <description><![CDATA[<p class="first">Patry digs into the evidence about copyright renewals and uncovers what every honest book publisher already knew:</p>

<cite class="bq"><a href="http://aworkinglibrary.com/library/book/how_to_fix_copyright/">Patry, <em>How to Fix Copyright</em>, page 205</a></cite>
<blockquote>
<p>
The failure to renew was an empirical, market signal about the value that copyright owners themselves placed on copyright. The renewal rates also showed a consistent difference in renewal rates for classes of works. The lowest renewal rates (0.4 percent) were for technical drawings, lectures, sermons, and other oral works. The highest renewal rate was for motion pictures (74 percent). Music was 48 percent and books only 7 percent. Our current one-size-fits-all approach ignores this significant data about how copyright owners have themselves valued copyright. Based on this evidence, the correct term of copyright should vary depending on the type of material being protected, with books getting a shorter term than motion pictures.
</p>
</blockquote>

<p class="first">Even with a term of copyright of only fourteen years (the original term in the States), most books would not be renewed, because most books are no longer worth much after that period of time. Failing to let them come into the public domain only makes them inaccessible&#8212;that is, invisible. A book can have an immense cultural value for centuries past the point at which it's already anemic financial value has passed. The obscene copyright term now in place serves no financial gain, and yet manages to rob us nonetheless.</p>]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-03-26T13:25:35+00:00</dc:date>
    </item>

    <item>
      <title>The Frankies Spuntino Kitchen Companion and Cooking Manual</title>
      <link>http://aworkinglibrary.com/feeder/?FeederAction=clicked&amp;feed=Reading&amp;seed=http%3A%2F%2Faworkinglibrary.com%2Flibrary%2Fbook%2Ffrankies_spuntino_kitchen_companion_and_cooking_manual%2F&amp;seed_title=The+Frankies+Spuntino+Kitchen+Companion+and+Cooking+Manual</link>
      <description><![CDATA[From one of my favorite local restaurants comes a lovely and instructive manual. An entire chapter is devoted to making Sunday sauce, complete with a timeline for the day. Do make the braciola.<img src="http://www.aworkinglibrary.com/images/covers/falcinelli-frankies-sputino.jpg" class="cover" alt="book_cover" width="320" height="479" /> ]]></description>
      <dc:subject>Artisan, Frank Castronovo, Frank Falcinelli, Peter Meehan, Food</dc:subject>
      <dc:date>2012-03-18T23:15:50+00:00</dc:date>
    </item>

    <item>
      <title>Making copies</title>
      <link>http://aworkinglibrary.com/feeder/?FeederAction=clicked&amp;feed=Reading&amp;seed=http%3A%2F%2Faworkinglibrary.com%2Flibrary%2Farchives%2Fmaking_copies%2F&amp;seed_title=Making+copies</link>
      <description><![CDATA[<p class="first">What it means to make a copy:</p>

<cite class="bq"><a href="">Patry, <em>How to Fix Copyright</em>, page 99</a></cite>
<blockquote>
<p>
The most damaging consequence of the movement to turn culture into private property is the largely successful change in attitude toward creativity and copying. Creative people are supposedly those who do not copy or imitate others. As we just saw, this is false; creative people <em>must copy and must imitate others</em>. Treating transformative copying as theft, as laziness, or as being non-creative is counter to human nature. All learning is social; copying is an essential form of social learning. Our copyright laws must be changed to reflect this fact.
</p>
</blockquote>

<p class="first">Emphasis mine; this is perhaps the most distressing part of the conversations around <a href="http://en.wikipedia.org/wiki/Stop_Online_Piracy_Act">SOPA and PIPA</a> and similar bills put forth by the <a href="http://steveblank.com/2012/01/04/why-the-movie-industry-cant-innovate-and-the-result-is-sopa/">entertainment industry</a>. It is inconceivable that a group of people whose primary livelihood depends on remakes could misunderstand this most basic element of creativity. More likely that they recognize the value that such a ruling could infer on their own back catalog. Put another way: copying in order to make anew is not lazy. But relying on revenue from copies of your own work most certainly is.</p>]]></description>
      <dc:subject></dc:subject>
      <dc:date>2012-03-06T17:38:31+00:00</dc:date>
    </item>

    <item>
      <title>How to Fix Copyright</title>
      <link>http://aworkinglibrary.com/feeder/?FeederAction=clicked&amp;feed=Reading&amp;seed=http%3A%2F%2Faworkinglibrary.com%2Flibrary%2Fbook%2Fhow_to_fix_copyright%2F&amp;seed_title=How+to+Fix+Copyright</link>
      <description><![CDATA[Patry is senior copyright counsel at Google, and despite the upfront disclaimer, this book defines a vision of copyright that clearly benefits the world's biggest search engine. That bias aside, the vision is clear-headed, practical, and scientific&#8212;quite refreshing in light of the current SOPA/PIPA frothing-at-the-mouth coming from other corners. A solid complement to Hyde's <a href="http://aworkinglibrary.com/library/book/common_as_air/"><em>Common as Air</em></a>.<img src="http://www.aworkinglibrary.com/images/covers/patry-how-to-fix-copyright.jpg" class="cover" alt="book_cover" width="320" height="492" /> ]]></description>
      <dc:subject>Oxford University Press, William Patry</dc:subject>
      <dc:date>2012-03-06T17:15:06+00:00</dc:date>
    </item>

    <item>
      <title>Books as History</title>
      <link>http://aworkinglibrary.com/feeder/?FeederAction=clicked&amp;feed=Reading&amp;seed=http%3A%2F%2Faworkinglibrary.com%2Flibrary%2Fbook%2Fbooks_as_history%2F&amp;seed_title=Books+as+History</link>
      <description><![CDATA[If you can get past the absolutely reprehensible cover design, <em>Books as History</em> is a smart study of books' physical form, and a defense of its value independent of the words on the page. Whether or not the printed book "survives" is a less interesting question to me than what we can learn from books as they have been and are now becoming, and Pearson's text is a succinct tale of the former. As for the latter, we'll all know in time. <img src="http://www.aworkinglibrary.com/images/covers/pearson-books-as-history.jpg" class="cover" alt="book_cover" width="320" height="416" /> ]]></description>
      <dc:subject>Oak Knoll Press, David Pearson</dc:subject>
      <dc:date>2011-12-19T15:09:55+00:00</dc:date>
    </item>

    <item>
      <title>The Lifecycle of Software Objects</title>
      <link>http://aworkinglibrary.com/feeder/?FeederAction=clicked&amp;feed=Reading&amp;seed=http%3A%2F%2Faworkinglibrary.com%2Flibrary%2Fbook%2Flifecycle_of_software_objects%2F&amp;seed_title=The+Lifecycle+of+Software+Objects</link>
      <description><![CDATA[As a novel, <em>The Lifecycle of Software Objects</em> suffers from expository writing, flat characters, and uninspired prose. But as a thought experiment, it's surprisingly (if incompletely) compelling. Chiang explores how we might teach an artificial intelligence, and what happens when (or if) it grows up. The ideas outshine the story. <img src="http://www.aworkinglibrary.com/images/covers/chiang-lifecycle-of-software-objects.jpg" class="cover" alt="book_cover" width="320" height="469" /> ]]></description>
      <dc:subject>Subterranean Press, Ted Chiang</dc:subject>
      <dc:date>2011-12-01T14:14:51+00:00</dc:date>
    </item>

    <item>
      <title>Names for the familiar</title>
      <link>http://aworkinglibrary.com/feeder/?FeederAction=clicked&amp;feed=Reading&amp;seed=http%3A%2F%2Faworkinglibrary.com%2Flibrary%2Farchives%2Fnames_for_the_familiar%2F&amp;seed_title=Names+for+the+familiar</link>
      <description><![CDATA[<p class="first">On designing with words:</p>

<cite class="bq"><a href="http://aworkinglibrary.com/library/book/community_and_privacy/">Chermayeff and Alexander, <em>Community and Privacy</em>, page 149</a></cite>
<blockquote><p>
In view of the conceptual changes that are taking place it is hardly helpful to continue using in connection with housing problems words that are firmly anchored in the cultures of days gone by; they can only mislead us in our present search for better solutions. "Apartments," "row houses," "single-family houses," "yard," "garden," "garbage," "parking lot," "living room," "kitchen," "dining room," "bedroom," "bathroom," are all heavily loaded words that make ay number of irrelevant images spring to mind. Designer and user alike may imagine that these words stand for something immutable, though in fact they are just names for the familiar. </p>
<p>Until one stops using popular or generalized words to describe specific objects and events, one will continue to be deceived by the associations with them and will fail to arrive at the essential functional aspect of things and places that is the planner's actual concern in problem-analysis and design.
</p></blockquote>

<p class="first">I start nearly every design project with words. Words define the problem and its scope, and they pave the way towards a solution. Names are especially important, as what you call things will prescribe how you approach them. One trick I've found that often works is to look to vocabulary from another domain; so, if you're designing a bedroom, use words from landscape architecture; or if you're designing a book, use cooking words. The end result may or may not be useful, but the exploration itself is often illustrative.</p>]]></description>
      <dc:subject></dc:subject>
      <dc:date>2011-11-29T14:26:38+00:00</dc:date>
    </item>

    <item>
      <title>The interstices</title>
      <link>http://aworkinglibrary.com/feeder/?FeederAction=clicked&amp;feed=Reading&amp;seed=http%3A%2F%2Faworkinglibrary.com%2Flibrary%2Farchives%2Fthe_interstices%2F&amp;seed_title=The+interstices</link>
      <description><![CDATA[<p class="first">How do you approach a problem? </p>

<cite class="bq"><a href="http://aworkinglibrary.com/library/book/community_and_privacy">Chermayeff and Alexander, <em>Community and Privacy</em>, page 159</a></cite>
<blockquote><p>
This is the crucial question in any design process, for countless different views of the problem are possible. The most fruitful aspects to consider, can we but identify them, are those most deeply related to the structure of the problem. The sense in which the structure given by the grouping of parts can help us solve a problem is illustrated beautifully in the words of Chuangtzu, who lived at the time of Plato, put into the mouth of a Taoist butcher:</p>
<p>"A good cook changes his chopper once a year&#8212;because he cuts. An ordinary cook, once a month, because he hacks. But I have had this chopper nineteen years, and although I have cut up many thousand bullocks, its edge is as if fresh from the whetstone. For at the joints there are always interstices, and the edge of a chopper being without thickness, it remains only to insert that which is without thickness into such an interstice. By this means the interstice will be enlarged, and the blade will find plenty of room."</p>
</blockquote>

<p class="first">I love this. Think about the problems you are trying to solve. Look closely&#8212;look at how all the pieces fit together, and then see where there is room for you to insert your blade.</p>]]></description>
      <dc:subject></dc:subject>
      <dc:date>2011-11-28T15:54:05+00:00</dc:date>
    </item>

    
    </channel>
</rss>
