<?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: Less crack today&#8230;</title>
	<atom:link href="http://blogs.gnome.org/hughsie/2007/03/25/less-crack-today/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/hughsie/2007/03/25/less-crack-today/</link>
	<description>Blog about geeky stuff</description>
	<lastBuildDate>Sun, 29 Jan 2012 09:38:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Anonymous</title>
		<link>http://blogs.gnome.org/hughsie/2007/03/25/less-crack-today/comment-page-1/#comment-63</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sun, 25 Mar 2007 20:58:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/2007/03/25/less-crack-today/#comment-63</guid>
		<description>In shipping versions, the applet will confidently claim that there are, say, one hour and 47 minutes remaining, giving three digits of precision when we know that the estimate is nowhere near that accurate. What if you communicated with digits of precision?  You might report 1:47 for a battery that you have a good history for, and just say &quot;about 2 hours&quot; when someone plugs in a new battery that claims to be fully charged, but that you have no profile for.  The underlying model would be that you have an estimate and error bars, and you find a way in the display to communicate about the error bars: report a round number that&apos;s in the interior of the region, don&apos;t report more significant figures than you have, and add the modifier &quot;about&quot; if there isn&apos;t even one digit of precision.</description>
		<content:encoded><![CDATA[<p>In shipping versions, the applet will confidently claim that there are, say, one hour and 47 minutes remaining, giving three digits of precision when we know that the estimate is nowhere near that accurate. What if you communicated with digits of precision?  You might report 1:47 for a battery that you have a good history for, and just say &#8220;about 2 hours&#8221; when someone plugs in a new battery that claims to be fully charged, but that you have no profile for.  The underlying model would be that you have an estimate and error bars, and you find a way in the display to communicate about the error bars: report a round number that&apos;s in the interior of the region, don&apos;t report more significant figures than you have, and add the modifier &#8220;about&#8221; if there isn&apos;t even one digit of precision.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  blogs.gnome.org/hughsie/2007/03/25/less-crack-today/feed/ ) in 0.14971 seconds, on Feb 12th, 2012 at 3:07 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 12th, 2012 at 4:07 am UTC -->
