<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Three Lessons From Tufte: Special Deliverable #6</title>
	<atom:link href="http://boxesandarrows.com/three-lessons-from-tufte-special-deliverable-6/feed/" rel="self" type="application/rss+xml" />
	<link>http://boxesandarrows.com/three-lessons-from-tufte-special-deliverable-6/</link>
	<description>Boxes and Arrows is devoted to the practice, innovation, and discussion of design; including graphic design, interaction design, information architecture and the design of business.</description>
	<lastBuildDate>Wed, 15 May 2013 11:41:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Chris McEvoy</title>
		<link>http://boxesandarrows.com/three-lessons-from-tufte-special-deliverable-6/#comment-8946</link>
		<dc:creator>Chris McEvoy</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/three-lessons-from-tufte-special-deliverable-6/#comment-8946</guid>
		<description><![CDATA[On Authorship:
It is important to know &quot;who did that&quot; - and it&#039;s a much bigger issue than simply &quot;denial of the author&#039;s rights&quot;.
It is extremely important for makers to know about other makers - and for users to know who made the things they use.
Dust or Magic by Bob Hughes

Signing our work creates a connection between the developer and the user.
The user can see who created the software and how to get in touch with that person.
Software Craftmanship by Pete McBreen

On Data:
I have been grappling with data presentation for years, and have definitely found that subtle effects which &quot;encourage the eye&quot; are much better than the bold-mania approach where data is forced on the user like that power tool in driller-killer.

My latest attempts at data presentation can be found at usabilityviews.com (there is a BAA page)]]></description>
		<content:encoded><![CDATA[<p>On Authorship:<br />
It is important to know &#8220;who did that&#8221; &#8211; and it&#8217;s a much bigger issue than simply &#8220;denial of the author&#8217;s rights&#8221;.<br />
It is extremely important for makers to know about other makers &#8211; and for users to know who made the things they use.<br />
Dust or Magic by Bob Hughes</p>
<p>Signing our work creates a connection between the developer and the user.<br />
The user can see who created the software and how to get in touch with that person.<br />
Software Craftmanship by Pete McBreen</p>
<p>On Data:<br />
I have been grappling with data presentation for years, and have definitely found that subtle effects which &#8220;encourage the eye&#8221; are much better than the bold-mania approach where data is forced on the user like that power tool in driller-killer.</p>
<p>My latest attempts at data presentation can be found at usabilityviews.com (there is a BAA page)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
