<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Book on Evan Hoffman</title><link>https://evan.wtf/tags/book/</link><description>Recent content in Book on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Tue, 26 Apr 2011 17:20:21 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/book/index.xml" rel="self" type="application/rss+xml"/><item><title>JavaScript: The Good Parts</title><link>https://evan.wtf/2011/04/26/javascript-the-good-parts/</link><pubDate>Tue, 26 Apr 2011 17:20:21 +0000</pubDate><guid>https://evan.wtf/2011/04/26/javascript-the-good-parts/</guid><description>&lt;p&gt;I just finished reading &lt;a href="http://www.amazon.com/gp/product/0596517742/ref=as_li_ss_tl?ie=UTF8&amp;amp;tag=evanhoffmasho-20&amp;amp;linkCode=as2&amp;amp;camp=217145&amp;amp;creative=399349&amp;amp;creativeASIN=0596517742"&gt;JavaScript: The Good Parts&lt;/a&gt;, one of the best programming books I&amp;rsquo;ve read. The ending is fantastic:&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;We see a lot of feature-driven product design in which the cost of features is not properly accounted. Features can have a negative value to consumers because they make the products more difficult to understand and use. We are finding that people like products that just work. It turns out that designs that just work are much harder to produce than designs that assemble long lists of features.&lt;/p&gt;</description></item></channel></rss>