<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Ephram Zerb</title>
	
	<link>http://ephramzerb.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Thu, 12 Aug 2010 18:53:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/EphramZerb" /><feedburner:info uri="ephramzerb" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>Getting Rid of Stuff</title>
		<link>http://feedproxy.google.com/~r/EphramZerb/~3/YNfWxMWePvk/</link>
		<comments>http://ephramzerb.com/2010/08/getting-rid-of-stuff/#comments</comments>
		<pubDate>Thu, 12 Aug 2010 18:53:37 +0000</pubDate>
		<dc:creator>Ephram Zerb</dc:creator>
				<category><![CDATA[Quote]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Product]]></category>

		<guid isPermaLink="false">http://ephramzerb.com/?p=506</guid>
		<description><![CDATA[The enabling features aren&#8217;t obvious and evident, because the key was getting rid of stuff. &#8211; Jonathan Ive, on designing the iPod [Wired]]]></description>
			<content:encoded><![CDATA[<blockquote><p>The enabling features aren&#8217;t obvious and evident, because the key was getting rid of stuff.</p></blockquote>
<p><cite>&#8211;  Jonathan Ive, on designing the iPod [<a href="http://www.wired.com/gadgets/mac/commentary/cultofmac/2006/10/71956?currentPage=all">Wired</a>]</cite></p>
]]></content:encoded>
			<wfw:commentRss>http://ephramzerb.com/2010/08/getting-rid-of-stuff/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://ephramzerb.com/2010/08/getting-rid-of-stuff/</feedburner:origLink></item>
		<item>
		<title>Propositional Density</title>
		<link>http://feedproxy.google.com/~r/EphramZerb/~3/923uxGzL7rA/</link>
		<comments>http://ephramzerb.com/2010/07/propositional-density/#comments</comments>
		<pubDate>Mon, 26 Jul 2010 19:51:17 +0000</pubDate>
		<dc:creator>Ephram Zerb</dc:creator>
				<category><![CDATA[Original]]></category>

		<guid isPermaLink="false">http://ephramzerb.com/?p=477</guid>
		<description><![CDATA[I&#8217;ve long held that design can be evaluated on fairly objective grounds: there is wrong, right and shades in between. For example, what constitutes a wrong is an element or a motif that does not add to the cohesiveness of the communication. I have a hard time departing from an established visual language. If a [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve long held that design can be evaluated on fairly objective grounds: there is wrong, right and shades in between.  </p>
<p>For example, what constitutes a wrong is an element or a motif that does not add to the cohesiveness of the communication.  I have a hard time departing from an established visual language. If a link is blue, it makes sense for all links to be blue.  If the color yellow is used to express &#8220;you are here&#8221;, it dilutes the communication to use it in another fashion.  (This is an over-simplification and you can lean on things like context and established convention to bend the rules, but the concept remains).</p>
<p>In other words, what I&#8217;ve been doing is reducing design components to their atomic unit, attaching meaning to them, and using these basic building blocks to define the visual language.</p>
<p>However, what I consider good design is usually a bit more textured than the above methodology can justify.  A better model for evaluating design is propositional density, which I&#8217;ll let <a href="http://well-formed-data.net/archives/495/propositional-density-in-visualization">Moritz Stefaner</a> describe using the Fed Ex logo as an example:</p>
<blockquote><p>Let us start with the notion of a proposition: in this context, a proposition is simply an elementary, atomic statement about the object at hand. “The FedEx logotype is purple” and “The FedEx logotype is set in a sans-serif font” are propositions, and because they describe salient, perceptible properties of the design, they are referred to as <strong>surface propositions</strong>.</p>
<p>Now, the FedEx logo became famous for a perceptual trick: The white space between the E and the x creates an arrow. This arrow induces, by its semiotic reading, a number of additional associations and readings of the design: “FedEx is on the go”, “FedEx is forward-thinking”, etc. Note that these propositions, unlike the surface propositions, are much harder to enumerate as they depend on the meaning that the observer ascribes to the arrow. These are called <strong>deep propositions</strong> as they describe underlying and often hidden meanings of the design. You can think of an iceberg, where the surface propositions are over the water – easy to see and clear cut – but the much larger part is under water.
</p></blockquote>
<p>These two concepts can be combined into a simple formula to calculate <strong>propositional density</strong>: # deep propositions / # surface propositions. </p>
<blockquote><p>Generally speaking, good design usually has a high propositional density. On the other hand, if your propositional density is below one, you probably have superfluous, merely decorative elements in your design, which do not add to the deep reading.</p></blockquote>
<p>Attempting to calculate this is neither practical or precise, but the recognition of deep propositions allows us to escape a rigorous system like the one I described and dabble in design elements that I would otherwise discard as decoration.</p>
]]></content:encoded>
			<wfw:commentRss>http://ephramzerb.com/2010/07/propositional-density/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://ephramzerb.com/2010/07/propositional-density/</feedburner:origLink></item>
		<item>
		<title>monome</title>
		<link>http://feedproxy.google.com/~r/EphramZerb/~3/E6_L-_em3d0/</link>
		<comments>http://ephramzerb.com/2010/01/monome/#comments</comments>
		<pubDate>Fri, 08 Jan 2010 10:32:17 +0000</pubDate>
		<dc:creator>Ephram Zerb</dc:creator>
				<category><![CDATA[Original]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Hackery]]></category>

		<guid isPermaLink="false">http://ephramzerb.com/?p=467</guid>
		<description><![CDATA[These monome devices, described as &#8220;adaptable, minimalist interfaces&#8221;, let you hack a grid of lights. The extreme design reduction liberates the device&#8217;s perceived potential. Adding any extra features to the device would be like replacing a blank canvas with a coloring book. The device is built by two people from the future, brian crabtree and [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://ephramzerb.com/images/posts/2010/01/monome-device.png" alt="monome-device" title="monome-device" width="480" height="320" class="size-full wp-image-468 bordered" /></p>
<p>These <a href="http://monome.org/devices">monome devices</a>, described as &#8220;adaptable, minimalist interfaces&#8221;, let you hack a grid of lights.  The extreme design reduction liberates the device&#8217;s perceived potential.  Adding any extra features to the device would be like replacing a blank canvas with a coloring book.  The device is built by two people from the future, brian crabtree and kelli cain, where capitalization has long been regarded as superfluous decoration.</p>
]]></content:encoded>
			<wfw:commentRss>http://ephramzerb.com/2010/01/monome/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		<feedburner:origLink>http://ephramzerb.com/2010/01/monome/</feedburner:origLink></item>
		<item>
		<title>API as User Interface</title>
		<link>http://feedproxy.google.com/~r/EphramZerb/~3/xeRuWqbFiYA/</link>
		<comments>http://ephramzerb.com/2009/12/api-as-user-interface/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 16:15:07 +0000</pubDate>
		<dc:creator>Ephram Zerb</dc:creator>
				<category><![CDATA[Quote]]></category>

		<guid isPermaLink="false">http://ephramzerb.com/?p=461</guid>
		<description><![CDATA[Moreover, an API is not about programming, data structures, or algorithms—an API is a user interface, just as much as a GUI. The user at the using end of the API is a programmer—that is, a human being. &#8211; Michi Henning, API Design Matters [via Jwatt]]]></description>
			<content:encoded><![CDATA[<blockquote><p>Moreover, an API is not about programming, data structures, or algorithms—an API is a user interface, just as much as a GUI. The user at the using end of the API is a programmer—that is, a human being.</p></blockquote>
<p><cite>&#8211; Michi Henning, <a href="http://cacm.acm.org/magazines/2009/5/24646-api-design-matters/fulltext">API Design Matters</a></cite></p>
<p>[via <a href="http://justinsomnia.org">Jwatt</a>]</p>
]]></content:encoded>
			<wfw:commentRss>http://ephramzerb.com/2009/12/api-as-user-interface/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://ephramzerb.com/2009/12/api-as-user-interface/</feedburner:origLink></item>
		<item>
		<title>Love / Hate, A / B</title>
		<link>http://feedproxy.google.com/~r/EphramZerb/~3/e9KNWb-ZVgs/</link>
		<comments>http://ephramzerb.com/2009/12/love-hate-a-b/#comments</comments>
		<pubDate>Wed, 09 Dec 2009 20:59:01 +0000</pubDate>
		<dc:creator>Ephram Zerb</dc:creator>
				<category><![CDATA[Original]]></category>

		<guid isPermaLink="false">http://ephramzerb.com/?p=454</guid>
		<description><![CDATA[I have a love / hate relationship with A / B tests. Leaning too hard on them to make design decisions can make for very anemic process. It encourages an incremental, guess-and-check approach that feels like a task better suited for an automaton. Even when isolating one variable, the results mainly speak to &#8220;what&#8221; had [...]]]></description>
			<content:encoded><![CDATA[<p>I have a love / hate relationship with A / B tests.  Leaning too hard on them to make design decisions can make for very anemic process.  It encourages an incremental, guess-and-check approach that feels like a task better suited for an automaton. Even when isolating one variable, the results mainly speak to &#8220;what&#8221; had the effect on behavior, rather than the &#8220;why&#8221;.  I&#8217;d rather be solving problems and taking bigger strokes.  But you simply can&#8217;t argue with its place in the toolbelt, especially when seeing <a href="http://www.abtests.com/test/38004/landing-for-geomoto">some of the results</a> on <a href="http://abtests.com">ABTests.com</a></p>
]]></content:encoded>
			<wfw:commentRss>http://ephramzerb.com/2009/12/love-hate-a-b/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://ephramzerb.com/2009/12/love-hate-a-b/</feedburner:origLink></item>
		<item>
		<title>Node.js Overview</title>
		<link>http://feedproxy.google.com/~r/EphramZerb/~3/-AyfrTpp-9o/</link>
		<comments>http://ephramzerb.com/2009/11/node-js-overview/#comments</comments>
		<pubDate>Tue, 24 Nov 2009 00:08:42 +0000</pubDate>
		<dc:creator>Ephram Zerb</dc:creator>
				<category><![CDATA[Link]]></category>
		<category><![CDATA[Hackery]]></category>

		<guid isPermaLink="false">http://ephramzerb.com/?p=449</guid>
		<description><![CDATA[Simon Willison is genuinely excited: That technology is Ryan Dahl’s Node. It’s the most exciting new project I’ve come across in quite a while. At first glance, Node looks like yet another take on the idea of server-side JavaScript, but it’s a lot more interesting than that. It builds on JavaScript’s excellent support for event-based [...]]]></description>
			<content:encoded><![CDATA[<p>Simon Willison is genuinely excited:</p>
<blockquote><p>That technology is <a href="http://nodejs.org/">Ryan Dahl’s Node</a>. It’s the most exciting new project I’ve come across in quite a while.</p>
<p>At first glance, Node looks like yet another take on the idea of server-side JavaScript, but it’s a lot more interesting than that. It builds on JavaScript’s excellent support for event-based programming and uses it to create something that truly plays to the strengths of the language.
</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://ephramzerb.com/2009/11/node-js-overview/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://simonwillison.net/2009/Nov/23/node/</feedburner:origLink></item>
		<item>
		<title>Basic Maths WordPress Theme</title>
		<link>http://feedproxy.google.com/~r/EphramZerb/~3/rWPl3O6Xx3k/</link>
		<comments>http://ephramzerb.com/2009/11/basic-maths-wordpress-theme/#comments</comments>
		<pubDate>Tue, 17 Nov 2009 19:32:25 +0000</pubDate>
		<dc:creator>Ephram Zerb</dc:creator>
				<category><![CDATA[Link]]></category>
		<category><![CDATA[Design]]></category>

		<guid isPermaLink="false">http://ephramzerb.com/?p=446</guid>
		<description><![CDATA[Beautiful new theme from Khoi Vinh and Allan Cole. It&#8217;s full-featured and comes equipped with everything you&#8217;d expect in a theme (although probably don&#8217;t need). The best part, which I&#8217;ll undoubtably be stealing for some future project, is the presentation of the archives in the right-most sidebar.]]></description>
			<content:encoded><![CDATA[<p>Beautiful new theme from <a href="http://subtraction.com/">Khoi Vinh</a> and <a href="http://fthrwght.com/">Allan Cole</a>.  It&#8217;s full-featured and comes equipped with everything you&#8217;d expect in a theme (although probably don&#8217;t need).  The best part, which I&#8217;ll undoubtably be stealing for some future project, is the presentation of the archives in the right-most sidebar.</p>
]]></content:encoded>
			<wfw:commentRss>http://ephramzerb.com/2009/11/basic-maths-wordpress-theme/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://basicmaths.subtraction.com/</feedburner:origLink></item>
		<item>
		<title>Real Relationships Drive Contribution</title>
		<link>http://feedproxy.google.com/~r/EphramZerb/~3/jf1MDGcQqq4/entry.asp</link>
		<comments>http://ephramzerb.com/2009/11/real-relationships-drive-contribution/#comments</comments>
		<pubDate>Tue, 10 Nov 2009 21:00:02 +0000</pubDate>
		<dc:creator>Ephram Zerb</dc:creator>
				<category><![CDATA[Link]]></category>
		<category><![CDATA[Product]]></category>

		<guid isPermaLink="false">http://ephramzerb.com/?p=441</guid>
		<description><![CDATA[The idea is that different types of online social relationships drive different levels of engagement. Whereas getting a lot of people to watch your youtube videos will encourage you to post more, you&#8217;re likely to get even a greater productivity boost if a lot of your actual friends favorite or comment on your videos. Luke [...]]]></description>
			<content:encoded><![CDATA[<p>The idea is that different types of online social relationships drive different levels of engagement.  Whereas getting a lot of people to watch your youtube videos will encourage you to post more, you&#8217;re likely to get even a greater productivity boost if a lot of your <em>actual</em> friends favorite or comment on your videos.   </p>
<p>Luke Wroblewski leaves it with a guess on why this is often the case:</p>
<blockquote><p>So actual friends (real relationships) are more likely to encourage contribution. Perhaps we can blame this on the <a href="http://www.cs.cornell.edu/home/kleinber/cacm08.pdf">0-1-2 effect</a> which states that the probability of joining an activity when two friends have done it is significantly more than twice the probability of doing it when only one has done so.
</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://ephramzerb.com/2009/11/real-relationships-drive-contribution/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://www.lukew.com/ff/entry.asp?939</feedburner:origLink></item>
		<item>
		<title>Reconsidering Arial</title>
		<link>http://feedproxy.google.com/~r/EphramZerb/~3/A62gLqVYzyU/reconsidering-arial</link>
		<comments>http://ephramzerb.com/2009/10/reconsidering-arial/#comments</comments>
		<pubDate>Thu, 08 Oct 2009 04:45:32 +0000</pubDate>
		<dc:creator>Ephram Zerb</dc:creator>
				<category><![CDATA[Link]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Typography]]></category>

		<guid isPermaLink="false">http://ephramzerb.com/?p=434</guid>
		<description><![CDATA[Jonathan Nicol does a nice job of visually demonstrating how Helvetica and Arial render at smaller sizes on a PC. My typical font stack has been Helvetica, followed by Arial; however, seeing Helvetica rendered at small sizes on a PC makes me reconsider that habit. The conclusion for me can be generalized as: use &#8220;Arial, [...]]]></description>
			<content:encoded><![CDATA[<p>Jonathan Nicol does a nice job of visually demonstrating how Helvetica and Arial render at smaller sizes on a PC. My typical font stack has been Helvetica, followed by Arial; however, seeing Helvetica rendered at small sizes on a PC makes me reconsider that habit.  The conclusion for me can be generalized as: use &#8220;Arial, Helvetica&#8221; for body copy and &#8220;Helvetica, Arial&#8221; for headings.</p>
]]></content:encoded>
			<wfw:commentRss>http://ephramzerb.com/2009/10/reconsidering-arial/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://f6design.com/journal/2009/09/30/reconsidering-arial</feedburner:origLink></item>
		<item>
		<title>Clever Hans and Usability Tests</title>
		<link>http://feedproxy.google.com/~r/EphramZerb/~3/-nE5qWoJefg/</link>
		<comments>http://ephramzerb.com/2009/09/clever-hans-and-usability-tests/#comments</comments>
		<pubDate>Tue, 01 Sep 2009 19:36:17 +0000</pubDate>
		<dc:creator>Ephram Zerb</dc:creator>
				<category><![CDATA[Link]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Research]]></category>

		<guid isPermaLink="false">http://ephramzerb.com/?p=429</guid>
		<description><![CDATA[Lukas Mathis retells a nice story that illustrates a hidden bias that can pollute a usability test. Clever Hans, his horse, quickly learned to do a number of complex math calculations &#8211; the horse could add, subtract, multiply, divide, do date calculations, and even understand German. It would tap out the answers to any math [...]]]></description>
			<content:encoded><![CDATA[<p>Lukas Mathis retells a nice story that illustrates a hidden bias that can pollute a usability test.</p>
<blockquote><p>Clever Hans, his horse, quickly learned to do a number of complex math calculations &#8211; the horse could add, subtract, multiply, divide, do date calculations, and even understand German. It would tap out the answers to any math question with its foot. It could even read and give the correct answers to questions written on a piece of paper.</p>
<p>Of course, when psychologist Oskar Pfungst investigated the horse, he quickly figured out what was happening. The horse didn’t understand German, couldn’t calculate, and couldn’t read. Instead, it responded to involuntary cues in the body language of Wilhelm von Osten, who, in turn, solved the math problems for his horse. Von Osten was completely unaware that he was providing these cues to the horse.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://ephramzerb.com/2009/09/clever-hans-and-usability-tests/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://ignorethecode.net/blog/2009/09/01/ruining-usability-tests/</feedburner:origLink></item>
	</channel>
</rss>
