<?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 2011</dc:rights>
    <dc:date>2011-11-29T14:26:38+00:00</dc:date>
    <admin:generatorAgent rdf:resource="http://expressionengine.com/" />
    

    <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>

    <item>
      <title>Community and Privacy</title>
      <link>http://aworkinglibrary.com/feeder/?FeederAction=clicked&amp;feed=Reading&amp;seed=http%3A%2F%2Faworkinglibrary.com%2Flibrary%2Fbook%2Fcommunity_and_privacy%2F&amp;seed_title=Community+and+Privacy</link>
      <description><![CDATA[A precursor to Alexander's <a href="http://aworkinglibrary.com/library/book/pattern_language/"><em>A Pattern Language</em></a>, in which he and Chermayeff define what's wrong with the design of the suburbs, and outline the principles behind a more human (and urban) environment. As interesting for its approach to the problem as it is for any of the proposed solutions. <img src="http://www.aworkinglibrary.com/images/covers/chermayeff-community-and-privacy.jpg" class="cover" alt="book_cover" width="320" height="535" /> ]]></description>
      <dc:subject>Anchor Books, Christopher Alexander, Serge Chermayeff</dc:subject>
      <dc:date>2011-11-28T15:53:01+00:00</dc:date>
    </item>

    <item>
      <title>The New Brooklyn Cookbook</title>
      <link>http://aworkinglibrary.com/feeder/?FeederAction=clicked&amp;feed=Reading&amp;seed=http%3A%2F%2Faworkinglibrary.com%2Flibrary%2Fbook%2Fnew_brooklyn_cookbook%2F&amp;seed_title=The+New+Brooklyn+Cookbook</link>
      <description><![CDATA[I use this less as a cookbook than as a guide for where to eat; but the recipes and photography are as lovely as the neighborhoods. A few favorites: the celery salad from Prime Meats; pickled eggs with jalape&ntilde;o from Beer Table; and the pecan pie sundae from Buttermilk Channel. <img src="http://www.aworkinglibrary.com/images/covers/vaugn-new-brooklyn-cookbook.jpg" class="cover" alt="book_cover" width="320" height="402" /> ]]></description>
      <dc:subject>William Morrow, Brendan Vaughn, Melissa Vaughn, Food</dc:subject>
      <dc:date>2011-11-27T15:30:20+00:00</dc:date>
    </item>

    <item>
      <title>Living and Eating</title>
      <link>http://aworkinglibrary.com/feeder/?FeederAction=clicked&amp;feed=Reading&amp;seed=http%3A%2F%2Faworkinglibrary.com%2Flibrary%2Fbook%2Fliving_and_eating%2F&amp;seed_title=Living+and+Eating</link>
      <description><![CDATA[A minimalist's manifesto, with simple recipes and beautiful, spare photography. Keeping it on my coffee table for perusing before heading to the farmer's market. <img src="http://www.aworkinglibrary.com/images/covers/pawson-living-and-eating.jpg" class="cover" alt="book_cover" width="320" height="414" /> ]]></description>
      <dc:subject>Clarkson Potter, Annie Bell, John Pawson, Food</dc:subject>
      <dc:date>2011-11-27T15:12:48+00:00</dc:date>
    </item>

    <item>
      <title>In real life</title>
      <link>http://aworkinglibrary.com/feeder/?FeederAction=clicked&amp;feed=Reading&amp;seed=http%3A%2F%2Faworkinglibrary.com%2Flibrary%2Farchives%2Fin_real_life%2F&amp;seed_title=In+real+life</link>
      <description><![CDATA[<p class="first">We have this phrase&#8212;&#8220;in real life&#8221;&#8212;to distinguish between the life that goes on in our pockets and the one that happens on the street. In theory, it privileges our most important relationships, the ones where we see people every day (or nearly so). But the obvious corollary to a "faux" life grates more and more each day. Is life online necessarily less real?</p>

<p>Zinsser writes that "the product that any writer has to sell is not the subject being written about, but who he or she is." Meaning, the best writing is an expression of the writer's self, a peek into their obsessions or fears. This is why an article on a topic for which you care little can be engrossing; what you are drawn to is not the subject matter, but the person telling the story. </p>

<p>And this is just as true of so-called frivolous writing on the web as it is of more crafted writing, including the offhand writing of a tweet or status update. The content of a particular tweet isn't what's valuable or interesting; it's the person it reveals. Some deride this as false intimacy&#8212;as creating the sense that you know someone when in fact you do not. But I think that's a mistake. It is not a <em>complete</em> intimacy, but it is a <em>true</em> one. </p>]]></description>
      <dc:subject></dc:subject>
      <dc:date>2011-11-09T12:47:04+00:00</dc:date>
    </item>

    <item>
      <title>On Writing Well</title>
      <link>http://aworkinglibrary.com/feeder/?FeederAction=clicked&amp;feed=Reading&amp;seed=http%3A%2F%2Faworkinglibrary.com%2Flibrary%2Fbook%2Fon_writing_well%2F&amp;seed_title=On+Writing+Well</link>
      <description><![CDATA[I'm only just now reading this book, but it was a bit like discovering an old friend you didn't know you had. Zinsser's is the kind of casual, unassuming writing that sounds effortless, but isn't. I tend not to read (or recommend) books on writing, as the best education you can have is just to read great books. But I'll make this an exception. <img src="http://www.aworkinglibrary.com/images/covers/zinsser-writing-well.jpg" class="cover" alt="book_cover" width="320" height="483" /> ]]></description>
      <dc:subject>Harper, William Zinsser</dc:subject>
      <dc:date>2011-11-09T12:29:10+00:00</dc:date>
    </item>

    <item>
      <title>Mobile First</title>
      <link>http://aworkinglibrary.com/feeder/?FeederAction=clicked&amp;feed=Reading&amp;seed=http%3A%2F%2Faworkinglibrary.com%2Flibrary%2Fbook%2Fmobile_first%2F&amp;seed_title=Mobile+First</link>
      <description><![CDATA[The sixth book from A Book Apart features data-driven techniques and best practices for designing for mobile from the inimitable Luke Wroblewski. It also represents the best kind of short book: packed with information and a delightful read. <img src="http://www.aworkinglibrary.com/images/covers/wroblewskii-mobile-first.jpg" class="cover" alt="book_cover" width="320" height="502" /> ]]></description>
      <dc:subject>A Book Apart, Luke Wroblewski</dc:subject>
      <dc:date>2011-10-18T14:20:26+00:00</dc:date>
    </item>

    
    </channel>
</rss>
