<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	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/"
	>

<channel>
	<title>Joel Cory: Blog &#187; reliability</title>
	<atom:link href="http://joelcory.com/blog/category/reliability/feed/" rel="self" type="application/rss+xml" />
	<link>http://joelcory.com</link>
	<description>Design, Develop, Illustrate, Photograph</description>
	<lastBuildDate>Sat, 26 Feb 2011 16:47:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<atom:link rel='hub' href='http://joelcory.com/?pushpress=hub'/>
		<item>
		<title>Sleeping with the enemy &#8211; I am running Windows 7</title>
		<link>http://joelcory.com/blog/2009/09/26/sleeping-with-the-enemy-i-am-running-windows-7/</link>
		<comments>http://joelcory.com/blog/2009/09/26/sleeping-with-the-enemy-i-am-running-windows-7/#comments</comments>
		<pubDate>Sat, 26 Sep 2009 21:03:57 +0000</pubDate>
		<dc:creator>Joel Cory</dc:creator>
				<category><![CDATA[bad design]]></category>
		<category><![CDATA[good design]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[reliability]]></category>
		<category><![CDATA[review]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[user interface design]]></category>
		<category><![CDATA[Vista]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[Windows 7]]></category>

		<guid isPermaLink="false">http://joelcory.com/?p=363</guid>
		<description><![CDATA[I never thought I&#8217;d see the day when I would upgrade past Windows XP, but it is here. Windows 7 RC is nice; it is almost bug free, fairly well organized, supports Direct X 10, and seems to support most of my hardware. Additionally, I felt no growing pains with my current level of RAM, [...]]]></description>
			<content:encoded><![CDATA[<p>I never thought I&#8217;d see the day when I would upgrade past Windows XP, but it is here. Windows 7 RC is nice; it is almost bug free, fairly well organized, supports Direct X 10, and seems to support most of my hardware. Additionally, I felt no growing pains with my current level of RAM, and system resources. It seems to be the best of XP and Vista put together.  But here&#8217;s the downside&#8230;<br />
<span id="more-363"></span><br />
As they say &#8220;all good things must come to an end&#8221; and Windows 7 RC is no more on my system. After the fifth day of daily BSODs (Blue Screens Of Death) I couldn&#8217;t take it anymore and wiped the system and put XP back on.  While I realize that this was not the final shipping product, it&#8217;s hard to make an unbiased assessment of a product that crashes this frequently. Here&#8217;s the rub, maybe the retail version will have these bugs worked out. If they don&#8217;t, how mad will I be having spent $100 for something this unstable. For a public release of a RC I wasn&#8217;t very impressed with the frequent crashes. I like Windows 7, but I&#8217;m not ready to plunk down my hard earned money especially with the experience I&#8217;ve had with it so far. Once again Microsoft has produced a product that I won&#8217;t trust until Service Pack 1.  For those that bought early&#8230; I&#8217;ll keep my fingers crossed for you.</p>
]]></content:encoded>
			<wfw:commentRss>http://joelcory.com/blog/2009/09/26/sleeping-with-the-enemy-i-am-running-windows-7/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Handcrafted CSS &#8211; and letting go of pixel perfection</title>
		<link>http://joelcory.com/blog/2009/09/19/handcrafted-css-cover/</link>
		<comments>http://joelcory.com/blog/2009/09/19/handcrafted-css-cover/#comments</comments>
		<pubDate>Sat, 19 Sep 2009 21:51:28 +0000</pubDate>
		<dc:creator>Joel Cory</dc:creator>
				<category><![CDATA[bad design]]></category>
		<category><![CDATA[Browsers]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[good design]]></category>
		<category><![CDATA[IE]]></category>
		<category><![CDATA[reliability]]></category>
		<category><![CDATA[review]]></category>
		<category><![CDATA[standards]]></category>
		<category><![CDATA[user interface design]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[web development]]></category>

		<guid isPermaLink="false">http://joelcory.com/?p=372</guid>
		<description><![CDATA[Handcrafted CSS, the latest contribution of Dan Cederholm to the world of Web Design and Development is a fantastic book! To say that I&#8217;m a fan of his work is a bit of an understatement. No web designer or developer should be without these books; Bulletproof Web Design, Handcrafted CSS, as well as Designing With [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://joelcory.com/blog/wp-content/uploads/2009/09/handcrafted-css-cover-150x150.jpg" alt="Handcrafted CSS" title="Handcrafted CSS" width="150" height="150" class="img" />Handcrafted CSS, the latest contribution of Dan Cederholm to the world of Web Design and Development is a fantastic book! To say that I&#8217;m a fan of his work is a bit of an understatement. No web designer or developer should be without these books; <a href="http://astore.amazon.com/simplebits-20/detail/0321509021">Bulletproof Web Design</a>, <a href="http://astore.amazon.com/simplebits-20/detail/0321643380">Handcrafted CSS</a>, as well as <a href="http://astore.amazon.com/simplebits-20/detail/0321385551">Designing With Web Standards</a>, and <a href="http://www.amazon.com/DOM-Scripting-Design-JavaScript-Document/dp/1590595335">DOM Scripting</a>. These books are fantastic resources, and push web development out of the dark ages of table based layout, css hacks, and duplicating sites for each browser version. But there is a particular philosophy the makes Handcrafted CSS special.<span id="more-372"></span></p>
<p>The philosophy of the book is move forward. Not through bleeding edge technologies but adherence and pioneering site development through standards. The way I see it, if web standards have been around long enough for Microsoft to finally adopt &#8211; than you have run out of excuses for adopting standards in your work. Validated standards compliant, non-table based layout, semantically driven web development is here, embrace it. </p>
<p>This book goes beyond that though. Handcrafted CSS is the add-on work that builds on the Bulletproof Web Design philosophy: Progressive enhancement. It works like this I&#8217;ve given up on pixel perfect cross-browser web development. I can no longer justify doubling my development time by crafting everything twice: once for standards based browsers, and again for IE. It&#8217;s expensive and for what benefit?  Think about it, besides the direct client and the developer, web site visitors use their browser, a single browser. They are not loading the site and switching back and forth between the two browsers scrutinizing every margin, border and font size. </p>
<p><em>Yes</em>, the site has to look good everywhere. <em>Yes</em>, it has to <strong>work </strong>in every browser. <strong><em>No</em></strong>, it does not have to look identical in every browser. Repeat this to yourself over and over until your breathing and heart rate returns to a normal level. I have come to realize that it will never look exactly the same, and the cost of getting it even as close as it is possible is not worth the time.</p>
<p>This is where Handcrafted CSS comes in. As soon as you let go of this old way of thinking an entire new world opens up. Modern, agile, browsers adopt standards early to allow for testing and contributing to the standards ratification process. The more developers exercise this code in their work, the stronger the final standards will be. We can prove out the efficacy of the standard everyday through our work. Additionally we are seeding the internet with millions of reasons to stop using IE all together.</p>
<p>I think that if web surfers knew that their world would be a richer, more beautiful place using standards based browsers, they would stop using IE. Additionally, the more the world swings in the direction of standards, the harder it will be for Microsoft to continue to do business as usual. They will be forced to join the party.</p>
<p>So if you are interested in furthering the standards movement, experience the wonder and awe of CSS3 and the freedoms it provides (not to mention the severe reduction of coding effort), there are three things you should do;</p>
<p>Buy Handcrafted CSS, adopt progressive enhancement as a philosophy, and create beautiful sites that illustrate the joys of letting go of the old ways of building web sites.</p>
]]></content:encoded>
			<wfw:commentRss>http://joelcory.com/blog/2009/09/19/handcrafted-css-cover/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Internet Explorer should die</title>
		<link>http://joelcory.com/blog/2009/03/03/internet-explorer-should-die/</link>
		<comments>http://joelcory.com/blog/2009/03/03/internet-explorer-should-die/#comments</comments>
		<pubDate>Tue, 03 Mar 2009 02:28:04 +0000</pubDate>
		<dc:creator>Joel Cory</dc:creator>
				<category><![CDATA[bad design]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[DOM]]></category>
		<category><![CDATA[Flash]]></category>
		<category><![CDATA[IE]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[reliability]]></category>
		<category><![CDATA[standards]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[web development]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://joelcory.com/blog/2009/03/02/internet-explorer-should-die/</guid>
		<description><![CDATA[Every now and then the festering issue of IE as a viable browser rears it&#8217;s ugly head. This eventuality usually occurs right around the release of a new version. Microsofts latest iteration, IE8, was slated to be released without standards mode being the default rendering mode. With all the progress that the web comunity has [...]]]></description>
			<content:encoded><![CDATA[<p>Every now and then the festering issue of IE as a viable browser rears it&#8217;s ugly head. This eventuality usually occurs right around the release of a new version. Microsofts latest iteration, IE8, was slated to be released without standards mode being the default rendering mode. With all the progress that the web comunity has made with standards why wouldn&#8217;t this be the default? <span id="more-91"></span>Months later, after more than a few angry articles, Microsoft has changed it&#8217;s mind and announced that &#8220;Super Standard Mode&#8221; will be the default rendering mode. </p>
<p>Good news for all. But it&#8217;s still too early to tell if this will be enough. There is still the issue of IE not embracing early adoption of CSS 3, and HTML 5. Most other standards based browsers have started supporting these future thinking standards and primed the web with example implementations and preparations for the inevitable switch. </p>
<p>What ever happened to &#8220;keeping up with the Joneses&#8221;? Let alone trying to pass up your competition. Heck Microsoft doesn&#8217;t even market a browser for Macintosh,the second largest growing operating system on the market. It&#8217;s even lost the browser wars on mobile devices with Safari (webkit) recently taking that crown. </p>
<p>It&#8217;s with these thoughts that I ask, is IE even worth the trouble? Maybe it should just go away and leave the innovation to the more relevant competitors on the web.   </p>
]]></content:encoded>
			<wfw:commentRss>http://joelcory.com/blog/2009/03/03/internet-explorer-should-die/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Firefox 3 and JSON</title>
		<link>http://joelcory.com/blog/2008/07/13/firefox-3-and-json/</link>
		<comments>http://joelcory.com/blog/2008/07/13/firefox-3-and-json/#comments</comments>
		<pubDate>Sun, 13 Jul 2008 23:54:55 +0000</pubDate>
		<dc:creator>Joel Cory</dc:creator>
				<category><![CDATA[Browsers]]></category>
		<category><![CDATA[reliability]]></category>
		<category><![CDATA[Scripting]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[web development]]></category>

		<guid isPermaLink="false">http://joelcory.com/blog/2008/07/13/firefox-3-and-json/</guid>
		<description><![CDATA[Has anyone else run into problems with their JSON and Firefox 3? We are rounding up development on one of the projects I am working on and Firefox 3 has thrown us a curve ball. Firefox 2, Safari 2.04, Safari 3, IE 6, IE 7 all test out fine on Mac and Windows.I have read [...]]]></description>
			<content:encoded><![CDATA[<p><img src='http://joelcory.com/blog/wp-content/uploads/2008/07/title-firefox1.thumbnail.png' alt='Firefox 3' class="img"/>Has anyone else run into problems with their JSON and Firefox 3? We are rounding up development on one of the projects I am working on and Firefox 3 has thrown us a curve ball. Firefox 2, Safari 2.04, Safari 3, IE 6, IE 7 all test out fine on Mac and Windows.I have read that there was a new JSON interpreter in FF3, but I expected new&#8230;to mean better, not broken. Any thoughts?</p>
]]></content:encoded>
			<wfw:commentRss>http://joelcory.com/blog/2008/07/13/firefox-3-and-json/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Don&#8217;t Buy Need for Speed Pro Street!</title>
		<link>http://joelcory.com/blog/2007/11/12/dont-buy-need-for-speed-pro-street/</link>
		<comments>http://joelcory.com/blog/2007/11/12/dont-buy-need-for-speed-pro-street/#comments</comments>
		<pubDate>Mon, 12 Nov 2007 00:11:08 +0000</pubDate>
		<dc:creator>Joel Cory</dc:creator>
				<category><![CDATA[bad design]]></category>
		<category><![CDATA[consumerism]]></category>
		<category><![CDATA[Marketing]]></category>
		<category><![CDATA[reliability]]></category>
		<category><![CDATA[review]]></category>

		<guid isPermaLink="false">http://joelcory.com/blog/2007/11/12/dont-buy-need-for-speed-pro-street/</guid>
		<description><![CDATA[I&#8217;ve had it! I bought Need for Speed Carbon the day it arrived in stores. I ran out after work handed over my hard earned cash and ran home to install it. It was fun, and I loved it. Sounds great. But the game crashes all the time. Random crashes, no warning, no error, straight [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve had it! I bought Need for Speed Carbon the day it arrived in stores. I ran out after work handed over my hard earned cash and ran home to install it. It was fun, and I loved it. Sounds great. But the game crashes all the time. Random crashes, no warning, no error, straight to desktop crashes. All the time. Patch 1.2, 1.3, 1.4, none of them do anything to improve the situation. I&#8217;ve reinstalled the game, Direct X, updated drivers all the recommended support tips. No good, still crashes. I started playing again, because I love the game and I bought it, and it still crashes. Because it&#8217;s random I can sometimes get through a fair bit before it crashes, other times one race. Sometimes in the car store, other times after cut scenes, the last time, which prompted me to write this, right in the middle of a race. ARGGGGHHH!!!!</p>
<p>Maybe it&#8217;s my system. Could be. But why wouldn&#8217;t Doom 3, Quake 4, Half-life 2, Tomb Raider, Bioshock, or Need for Speed underground, underground 2, or Most Wanted crash then too? In fact no other game I&#8217;ve played has crashed. My system is pretty much top of the line. Core 2 6400, 2Gb RAM, ATI 1900XTX 512Mb VRAM. </p>
<p>Why wouldn&#8217;t a company write a patch to resolve such a widespread, common problem. This is a well documented issue:</p>
<ul>
<li><a href="http://www.reaper-x.com/2007/01/18/need-for-speed-carbon-crash-to-desktop-issue/">reaper-x</a></li>
<li><a href="http://www.gameguru.in/pc/2006/21/need-for-speed-carbon-pc-patch-released-by-ea/">Gameguru</a></li>
<li><a href="http://www.neowin.net/forum/lofiversion/index.php/t508318-50.html">Neowin</a></li>
<li><a href="http://server1.megagames.com/news/show.cgi?&#038;idtype=patches&#038;database=697&#038;section=comments&#038;">Megagames</a></li>
<li><a href="http://www.overclock.net/pc-games/129011-need-speed-carbon-crashing-2.html">Overclock.net</a></li>
<li><a href="http://forums.guru3d.com/showthread.php?threadid=202020">Guru3d</a></li>
<li>Here is the full <a href="http://www.google.com/search?hl=en&#038;safe=off&#038;client=firefox-a&#038;rls=org.mozilla%3Aen-US%3Aofficial&#038;q=need+for+speed+carbon+%22Crash+to+desktop%22&#038;btnG=Search">Google results link</a></li>
</ul>
<p>I understand not knowing how to trace an un-reproducible bug, that doesn&#8217;t seem to be a problem here. I understand having hardware that doesn&#8217;t meet the system requirements, not an issue as far as I&#8217;ve read. I understand abandoning a project, not the case here as there have been three patches released since it launch. So what&#8217;s the problem?</p>
<p>More importantly I want to know why EA would think that I would actually buy the next installment of this game that comes out this week, Need for Speed Pro Street, when they haven&#8217;t even gotten the last one to work! I for one am waiting to buy this game until the user reviews come out, becasue even the game magazines didn&#8217;t report this problem with carbon. Buyer beware.</p>
<h3>Update</h3>
<p><a href='http://joelcory.com/blog/wp-content/uploads/2007/11/nfs-prostreet-crash.png' title='Crash Dialog' rel="lightbox[67]"><img src='http://joelcory.com/blog/wp-content/uploads/2007/11/nfs-prostreet-crash.thumbnail.png' alt='Crash Dialog' class="img" /></a>Right after I wrote this article, I found that the demo was online for Need For Speed Pro Street. I downloaded the 750 Mb file, installed it, and ran it. It trudged through the intro movies, flashy animations etc&#8230; Then I set my video setting to match my screen, this game at least supports my wide screen monitor, unlike Carbon. Setup my game pad. Then started the demo for the speed challenge. CRASH!!!!! I tried again, having to repeat all my setup procedures again. This time I quit after changing my settings, anticipating the crash and not want to set up my screen and controls again. Re-launched and tried again to start the race. CRASH!!!!!!!!! Wow, now I really want to buy this game. </p>
<p>Aren&#8217;t demos supposed to be the compelling, &#8220;oh my this is so amazing I have to play the full game&#8221; experience? The &#8220;this blew my mind, now I want to give them my credit card number&#8221; kind of experience? Oh well, guess I&#8217;ll save my money for the Orange Box, Crysis, or anything that doesn&#8217;t have the EA name on it. Pathetic!!!</p>
]]></content:encoded>
			<wfw:commentRss>http://joelcory.com/blog/2007/11/12/dont-buy-need-for-speed-pro-street/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Forget Gasoline&#8230;What about Plastic?</title>
		<link>http://joelcory.com/blog/2007/11/08/forget-gasolinewhat-about-plastic/</link>
		<comments>http://joelcory.com/blog/2007/11/08/forget-gasolinewhat-about-plastic/#comments</comments>
		<pubDate>Thu, 08 Nov 2007 23:00:39 +0000</pubDate>
		<dc:creator>Joel Cory</dc:creator>
				<category><![CDATA[bad design]]></category>
		<category><![CDATA[climate change]]></category>
		<category><![CDATA[consumerism]]></category>
		<category><![CDATA[education]]></category>
		<category><![CDATA[Industrial Design]]></category>
		<category><![CDATA[Marketing]]></category>
		<category><![CDATA[reliability]]></category>

		<guid isPermaLink="false">http://joelcory.com/blog/2007/11/08/forget-gasolinewhat-about-plastic/</guid>
		<description><![CDATA[One of the often overlooked problems with our dwindling oil future is plastic. As we continue to burn oil in our engines we are using a valuable resource that could be used for durable plastic goods. When the oil runs out, or becomes extremely rare and expensive, how will we manufacture plastics? We rely heavily [...]]]></description>
			<content:encoded><![CDATA[<p>One of the often overlooked problems with our dwindling oil future is plastic. As we continue to burn oil in our engines we are using a valuable resource that could be used for durable plastic goods. When the oil runs out, or becomes extremely rare and expensive, how will we manufacture plastics? We rely heavily on plastics for all our products; electronics, transportation,  medical technologies, construction, and housing. There are few things today that do not rely on plastics and polymers.<br />
<span id="more-66"></span><br />
Currently there are a number of technologies that are being developed that use vegetable oils to develop polymers. Many are promising. In the meantime we continue designing and manufacturing internal combustion engines. </p>
<p>Even if we move to corn/sugar ethanol, or even cellulosic ethanol we could be diverting our dependence on gasoline to another valuable resource that could be critical in alternative means to produce polymers. The truth is that we need to consider that burning things for propulsion is not a very efficient means to produce energy. </p>
<p>Combustion is a highly inefficient means to convert matter to energy. There are a lot of byproducts not only in the combustion process but the refining process as well. Additionally the friction and heat exchange of the engine, storage and transportation of the fuels, and the destructive means of extracting the fuels from the ground. It seems to be a pretty expensive way to move cars down the road. Most people don&#8217;t realize, but the price you pay at the pump is artificially lowered because the government subsidizes the gasoline industry. And for some time they have been subsidizing the ethanol industry as well. No one knows how expensive these fuels would be without the help of the government&#8217;s money.</p>
<p>So because we have committed to this path of consuming non-renewable resources to burn in our engines we may be rapidly eliminating our options for producing the products we have become highly dependent on. We all need to consider how our decisions shape the future, not only for our generation, but our children&#8217;s generation. The decisions we make today could have serious unintended consequences down the road. </p>
]]></content:encoded>
			<wfw:commentRss>http://joelcory.com/blog/2007/11/08/forget-gasolinewhat-about-plastic/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using Statistics to Lie</title>
		<link>http://joelcory.com/blog/2007/11/08/using-statistics-to-lie/</link>
		<comments>http://joelcory.com/blog/2007/11/08/using-statistics-to-lie/#comments</comments>
		<pubDate>Thu, 08 Nov 2007 22:42:34 +0000</pubDate>
		<dc:creator>Joel Cory</dc:creator>
				<category><![CDATA[education]]></category>
		<category><![CDATA[health]]></category>
		<category><![CDATA[Marketing]]></category>
		<category><![CDATA[reliability]]></category>

		<guid isPermaLink="false">http://joelcory.com/blog/2007/11/08/using-statistics-to-lie/</guid>
		<description><![CDATA[It&#8217;s amazing to me how many times I read an article and end up disagreeing with the conclusion. Not because I don&#8217;t like the results, but I don&#8217;t like how they arrived at the conclusion. For example I read an article stating that California leads the nation in motorcycle theft rates. This inflammatory article leaves [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s amazing to me how many times I read an article and end up disagreeing with the conclusion. Not because I don&#8217;t like the results, but I don&#8217;t like how they arrived at the conclusion. For example I read an article stating that <a href="https://www.nicb.org/cps/rde/xbcr/nicb/2006_Motorcycle_theft_report.rtf">California leads the nation in motorcycle theft rates</a>.<br />
<span id="more-64"></span><br />
This inflammatory article leaves out some critical facts, without which a true conclusion cannot be deduced. The fact is that California is a state where motorcyclists can ride almost year-round, these statistics don&#8217;t reflect this. The simple fact is that there are more bikes registered here than in most states.</p>
<p>For example:</p>
<p>Thefts in article: California (9,110)<br />
&#8220;Of the more than 28 million cars, light trucks and motorcycles registered in California, fewer than 600,000 (or about 2 percent) are motorcycles.&#8221; Monday, October 4, 2004 http://www.sfgate.com/cgi-bin/article.cgi?f=/c/a/2004/10/04/BAG9S93DBM1.DTL</p>
<p>Thats a <strong>1.51%</strong> theft rate.</p>
<p>Thefts in article: Florida (6,324)<br />
Registered motorcycles in Florida &#8220;in 2004 was approx. 410,439.&#8221; http://www.gaijinbikers.com/wp/</p>
<p>Thats a <strong>1.54%</strong> theft rate.</p>
<p>So even though there were &#8220;more bikes stolen&#8221; there was a lower percentage of bikes stolen. But unless a reader tears through all the facts, and reads the article with a critical eye they could be duped into believing anything.</p>
<p><a href='http://joelcory.com/blog/wp-content/uploads/2007/11/07fat_graphicfull.jpg' title='NYT Graphic for Obesity article' rel="lightbox[64]"><img src='http://joelcory.com/blog/wp-content/uploads/2007/11/07fat_graphicfull.thumbnail.jpg' alt='NYT Graphic for Obesity article' class="img" /></a></p>
<p>Here&#8217;s another example. The <a href="http://jama.ama-assn.org/cgi/content/abstract/298/17/2028?lookupType=volpage&#038;vol=298&#038;fp=2028&#038;view=short">JAMA Journal of American Medical Association (JAMA)</a> recently reported that being &#8220;overweight&#8221;, having a Body Mass Index (BMI) of 25-30, actually reduces your risk of death when compared to &#8220;underweight&#8221; people, BMI less than 18.5. Well the <a href="http://www.nytimes.com/2007/11/07/health/07fat.html?_r=1&#038;ref=health&#038;oref=slogin">New york times</a> ran with this, including an easy to read graphic, at left. </p>
<p>Now the rub. The article is clearly setting out that being overweight will reduce your chances of dying from respiratory disease, injuries, lung cancer, coronary heart disease and other cardiovascular diseases. The article doesn&#8217;t represent what other effects contribute to the numbers. Here is a great example.</p>
<p>BMI is a number derived from height and weight. I weigh 163 pounds, am 5&#8242; 9&#8243; and have a BMI of 24.1. Just under the Overweight category in this article. Where in this equation is body fat percentage? Not there. Body Mass Index is not a measure of body density, only height and weight. Fat is less dense than muscle, so an athletic person of 5&#8242; 9&#8243; would score a higher BMI, than an overweight person of 5&#8242; 9&#8243;. So using BMI alone for this data is a gross simplification of human anatomy and could lead people to the wrong conclusion. Being fat will not help you fight off these diseases and injuries. In all likelihood it will increase your risks, lower your quality of life, and introduce other health problems. More than likely being active, and more muscle toned (more dense, higher BMI) are the true cause of the decrease in deaths. </p>
<p>Think about it. When in your lifetime have you ever heard a report saying that being inactive was healthy? How many reports have you heard that indicate that obesity results in diabetes, heart failure, joint problems, loss of sex drive etc&#8230; Look at the longevity numbers for countries with lower obesity like Japan, and Europe. Clearly this article lacks clarity, and misinforms it&#8217;s readers.</p>
<p>These two examples, are just the tip of the iceberg. Statistics don&#8217;t lie, but they may lead you to false conclusions. The unfortunate side affect of neatly packaged generalizations is they don&#8217;t tell the whole story. When you lose all the little details you may be missing key facts that explain the real underlying system. As readers we all need to tear apart the &#8220;facts&#8221; and really analyze if there might be something else going on behind the numbers. Additionally the media, politicians, lobbyists, and most especially scientists need to do a better job of disclosing the full set of facts in these studies, clearly outlining where their data may be incomplete, and any factors that could be skewing the numbers. Until that happens its up to us, the readers, to read between the lines and become critical readers that don&#8217;t believe everything we see in print.</p>
]]></content:encoded>
			<wfw:commentRss>http://joelcory.com/blog/2007/11/08/using-statistics-to-lie/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Adobe Captivate V2 and V3 Review</title>
		<link>http://joelcory.com/blog/2007/11/02/adobe-captivate-v2-and-v3-review/</link>
		<comments>http://joelcory.com/blog/2007/11/02/adobe-captivate-v2-and-v3-review/#comments</comments>
		<pubDate>Fri, 02 Nov 2007 23:09:10 +0000</pubDate>
		<dc:creator>Joel Cory</dc:creator>
				<category><![CDATA[bad design]]></category>
		<category><![CDATA[Flash]]></category>
		<category><![CDATA[good design]]></category>
		<category><![CDATA[reliability]]></category>
		<category><![CDATA[web development]]></category>

		<guid isPermaLink="false">http://joelcory.com/blog/2007/11/02/adobe-captivate-v2-and-v3-review/</guid>
		<description><![CDATA[Getting back to design and development topics I thought it would be valuable to offer my insight on this product. Being a courseware developer over the last 11 years or so, I&#8217;ve worked with a lot of tools. For most courses developing in either HTML, or Flash or a combination of both is my preferred [...]]]></description>
			<content:encoded><![CDATA[<p>Getting back to design and development topics I thought it would be valuable to offer my insight on this product. Being a courseware developer over the last 11 years or so, I&#8217;ve worked with a lot of tools. For most courses developing in either HTML, or Flash or a combination of both is my preferred method. It offers a vast amount of control and creativity. These methods do require a higher level of skill in web development, animation, and scripting but the results are well worth the cost. On the other hand Adobe Captivate offers some flexibility and a relatively easy learning curve for developers, and instructional designers and can result in a very professional result. Here&#8217;s my take the good, the bad, and the ugly.<br />
<span id="more-62"></span></p>
<h3>The Good</h3>
<p>Adobe Captivate is a relatively easy tool to use. It is a cross between PowerPoint and Flash. It is slide based, like PowerPoint, but the animations appear on the screen based on timing set on a timeline, like Flash. This allows people who are familiar with PowerPoint to get started quickly.</p>
<p>The true power of Captivate lies in the ability to capture software interactions with mouse movement, and clicks. Very elaborate software simulations can be built quickly, and edited later for timing adjustments, and content additions. And the results are all in an interactive flash-based animation, not video.</p>
<p>My typical workflow with this tool starts with a script or storyboard detailing the path through the software, as well as the content for the annotations that I will add later. Next I open the application, website, or web based application, and Captivate. I set my capture size, and begin using the application following the script. Captivate follows along grabbing screens and mouse positions in the background. Once you are done capturing all the screens Captivate opens all the screens in a storyboard layout. Now I start editing the content, deleting redundant captures, editing the automated captions that Captivate generates, and inserting additional annotations. After everything is pared down and all the annotations are complete I record the audio (if any) and adjusting the timing of all the objects on the slide to match up with the audio.  The final step is publishing the whole thing to a flash animation. </p>
<p>I&#8217;ve worked with version one, and version two for a few years now. It&#8217;s easy to get quality results, and there are some great tricks to produce full blown web based trainings using this tool. On the market today there is no other tool that compares to the capabilities that Captivate offers, especially considering the editability, and flexibility. Unless you are going to produce full software simulations (everything works, just like the real software, all menus links etc.) Captivate is the tool to use.</p>
<h3>The Bad</h3>
<p>While this is an easy tool to use there are some limitations that can be worked around. There is no text tool, but there are captions. To create blocks of text you need to get a little creative and use a caption with a transparent background. This allows you to animate the text, fading in paragraphs, etc. Captivate offer a decent selection of caption styles and they do scale very well to contain the text without distorting, referred to as Scale 9 boxes. The corners remain unscaled as the sides scale. If you want to create your own caption styles you can. You create a .BMP file, and an accompanying .FCM file that specifies the boundaries of the Scale 9 box. Unfortunately these are BMP files so they don&#8217;t support transparency, and therefore there is no support for drop shadow on caption graphics. Imported graphics can be .PNG files and use transparency, but not captions. There are no drawing tools, diagramming tools, or photo retouching tools to crop images. Having a program like Fireworks is important if you want to do anything beyond what is in the box.</p>
<h3>The Ugly</h3>
<p>Version one had bugs that were resolved in version two&#8230;like rampant crashes. Version three is coming soon, but it doesn&#8217;t resolve all the bugs that are in two. To help you out here are a list of the bugs, and some workarounds that I have discovered in version two.</p>
<ol>
<li><strong>The awe inspiring file bloat bug:</strong> As you start adding content and saving your file the file size will grow. Expected. But what is unexpected is the the files growing to huge sizes 250Mb plus. We know this is aberrant behavior because of this workaround. Open a second instance of Captivate, and Copy the slides from the bloated file into the blank file and save. Poof all better, back to 50Mb. This bug does not affect the published flash files, just the project file.</li>
<li><strong>The incredible disappearing menus:</strong> At some point you will try to open a menu, usually after adding an animation, and the menus will open only to immediately close. The workaround click on an item in the library panel on the right side of the interface. Oh&#8230;you closed that, and now can&#8217;t open the menu to open it again&#8230; Use <ctrl> L to open the library again, then click on an item.</li>
<li><strong>The amazing crash-save bug:</strong> On more than one occasion I have completed capturing my screens in the application and Captivate has displayed an error-crash dialog threatening to wipe out all the work I just captured. Don&#8217;t panic! The software is still working behind the dialog box. Go to the File menu, and choose save, and name the file. Once it is all done saving click OK in the crash dialog to kill Captivate. All your work was saved and you can reopen Captivate and continue to work.</li>
<li><strong>The stupendous sound scrambler:</strong> On a couple occasions we have published projects and the audio has either repeated, or disappeared. Reviewing the project file the audio is there&#8230;republish gone, review there. After a few times doing this I realized that the application was broken. So I figured out that I needed to export the audio file to an MP3, delete it from the slide, and the library, then re-import it (or re-record it). Now it should publish properly.</li>
<li><strong>The dreadful dragging slide bug:</strong> I have tried to copy slides into a presentation and drag them in the storyboard view into their appropriate place in the slide order. They don&#8217;t always stay in order.  Sometimes they stay in a row, other times they forma column and intersperse all throughout the slides. Don&#8217;t try to drag multiple slides around&#8230;it&#8217;s ugly. The best solution is to go to the slide you want to place the slides after and import them from a seperate project file. Then they will populate in order.</li>
</ol>
<h3>Wrap up</h3>
<p>While I understand that Adobe acquired this product, and inherited some problems, they released version 2 without fixing them. Sad. Is it because they have no competition in this market so they feel safe that they have a captive audience? Maybe. Or have they been caught up in a feature race instead of fixing the bugs? I&#8217;m not the only one that has <a href="http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=67&#038;catid=464&#038;threadid=1254766&#038;enterthread=y">noticed these problems</a>. The general position of Adobe is that users need to file these issues with the <a href="http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&#038;product=15&#038;6213=9">bug and feature request form</a>. The serious question is whether you are willing to invest $700 dollars in a tool, only to work around the well documented bugs? I still like the tool despite these issues because of the results it produces, and the ease with which it produces those results.</p>
]]></content:encoded>
			<wfw:commentRss>http://joelcory.com/blog/2007/11/02/adobe-captivate-v2-and-v3-review/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to buy a bicycle</title>
		<link>http://joelcory.com/blog/2007/11/02/how-to-buy-a-bicycle/</link>
		<comments>http://joelcory.com/blog/2007/11/02/how-to-buy-a-bicycle/#comments</comments>
		<pubDate>Fri, 02 Nov 2007 20:21:06 +0000</pubDate>
		<dc:creator>Joel Cory</dc:creator>
				<category><![CDATA[bad design]]></category>
		<category><![CDATA[bicycling]]></category>
		<category><![CDATA[consumerism]]></category>
		<category><![CDATA[good design]]></category>
		<category><![CDATA[Industrial Design]]></category>
		<category><![CDATA[reliability]]></category>

		<guid isPermaLink="false">http://joelcory.com/blog/2007/11/02/how-to-buy-a-bicycle/</guid>
		<description><![CDATA[As a follow up to the article on cheap carbon frames I wanted to make a few additional points about bicycle quality that are less specific than one frame material. To begin, I think that everyone should ride bicycles. Bicycles provide low impact healthy exercise that is fun for all ages, and even more fun [...]]]></description>
			<content:encoded><![CDATA[<p>As a follow up to the article on <a href="http://joelcory.com/blog/2007/10/25/cheap-carbon-frames/">cheap carbon frames</a> I wanted to make a few additional points about bicycle quality that are less specific than one frame material. To begin, I think that everyone should ride bicycles. Bicycles provide low impact healthy exercise that is fun for all ages, and even more fun to do as a group. To get started you need to have a bicycle. If you already have one, or need to get one, here are some simple rules to follow when looking for a good bike.<br />
<span id="more-59"></span></p>
<h3>Go to a bike shop!</h3>
<p>This isn&#8217;t an elitist bike snob statement, it&#8217;s a statement made for your safety. Here&#8217;s why. When bicycles arrive from the manufacturer, they come in a box with some parts removed. The shop needs to assemble these parts and adjust them. Most department stores do not employ professional mechanics. That means that the stellar customer service you get at Walmart is assembling your bicycle. This is not a good thing. </p>
<h3>Parts aren&#8217;t parts</h3>
<p>Each part on the bicycle has a specific purpose. To illustrate this lets talk about brakes. Brakes slow you down and stop you from moving forward. If the brakes are of poor quality, or poorly adjusted, the results could be fatal. Stopping suddenly when a car cuts in front of you, or when the trail ends suddenly are not tasks that you want to entrust to cheap parts. Here is a test to see if you have good brakes, or if the bike you are shopping for has good brakes. Go into a department store, or out to your garage if you bought a department store bike, and try to bend the metal parts on the brakes with your bare hands. If they bend, or are loose, or the levers are loose or bend you have bad brakes. When you are rolling down the road and apply the brakes there are significant forces being exerted on the brakes. If your brakes are of poor quality, or badly adjusted they may not be up to the task.</p>
<p>So far I have just talked about the brakes but you can connect the dots for the rest of the parts: Poor quality = reduced reliability = increased safety risk = your life and health in the hands of a crappy collection of parts. Think about a few other consequences. Handlebars fail, you crash, maybe loosing your teeth or being run over by a car. Wheels fail, you could have a very long walk ahead of you. The frame breaks&#8230;you get the idea.</p>
<h3>What style of bike?</h3>
<p>Assuming that you have walked into your local bike shop, you are now confronted with having to choose between all the styles of bikes. While there are multiple choices they really break down to one thing, where do you want to ride? If you want to ride on park trails, paved and unpaved, or in the city at a slower pace, a hybrid may be the best bet. Hybrids have smooth tires that are fat like a mountain bike. They have upright handlebars for good visibility. These are great bikes for everyone. Now here are the guidelines for straying from the hybrid. If you want to go fast, or far on the road, get a road bike. If your idea of a trail is more dirt, rock, and ruts get a mountain bike. This is a great set of general guidelines to start with. To hone in on the exact bike from the three styles talk to a bike shop or email me and I&#8217;ll try to answer your more specific questions.</p>
<h3>How much to spend?</h3>
<p>As the old adage goes, &#8220;you get what you pay for&#8221;. But what are you paying for? With bicycles you are getting reliability, durability, weight, and longevity. The more you pay the better these qualities become to a point. Unless you are racing in the Tour De France, or training as hard as the pros do, you probably don&#8217;t need the top of the line parts (components). Unless you are planning to never ride don&#8217;t get the bottom of the line either. The middle ground is a nice safe place to start looking. Think of it this way, if you fall in love with the sport do you want to go out and buy a new bike right away because you cut some corners? Do you want to spend out for the de-luxe bling only to be depressed every time you look at the bike and realize that you never ride it? Do some shopping and ask questions. Down the road when you are totally committed and it becomes a lifestyle then you can re-invest in a top of the line bike, and keep the old one for trips around town and locking up to the bike rack.</p>
<p>If you are an established rider I recommend either Ultegra, or 105, unless you can settle for nothing but top of the line. I can personally testify that Ultegra will last nearly forever and it is very reliable. 105 won&#8217;t last quite as long, and is a little heavier, but if you&#8217;re on a budget, can&#8217;t wait to save up another few hundred dollars, and don&#8217;t want a used bike, 105 is a good option. The same is true in mountain bikes. Aim for XT, or LX. Both are great component sets, and follow the same logic as the road groups I&#8217;ve mentioned. Ten years ago I could have stopped there but there are new players in town, SRAM and Sampson and they are looking to be fantastic products with the same level of quality as their Japanese competitors. Last, but not least Campagnolo. This venerable manufacturer was and is the Ferrari of bicycle parts. They have always had great quality and reliability but were tended to be on the expensive side. I personally haven&#8217;t ridden anything newer than Nuevo Record&#8230;that from the 60&#8242;s so it&#8217;s hardly relevant. Because they tend to run on the expensive side most mid-level bicycles are not equipped with Campy parts. They tend to reside on the high end bikes exclusively. With any of these choices, ride them. The only way to tell which one you like is to ride the ones you don&#8217;t like.</p>
<h3>Which Brand?</h3>
<p>The second most common question is &#8220;Is this a good brand?&#8221; Sure. If you&#8217;re looking at a bike shop it&#8217;s probably a good brand. Many of the manufacturers have their bikes made in the same factory in Taiwan, or China. So even if the sticker says Brand X, or Y the same company probably put it all together. This is even more true of the mid to low range of bikes. As the bikes get more expensive there is more variety in the manufacturers and your shopping gets trickier. If you&#8217;re riding at that level you can read the magazines, talk to friends, and go on test rides to help you decide.</p>
<h3>Buy your accessories</h3>
<p>When you purchase your bike buy all the accessories you will need. Here&#8217;s a list:</p>
<ul>
<li>helmet</li>
<li>gloves</li>
<li>tubes</li>
<li>tire levers</li>
<li>patch kit</li>
<li>seat bag</li>
<li>tire pump</li>
<li>bottles</li>
<li>bottle cages</li>
<li>padded bike shorts</li>
</ul>
<p>Not only should you be able to get a deal on these items when you purchase them with a bike, you need them. These accessories will all make you ride more comfortable, safer, and allow you to avoid being broken down on the trail or road. Even if you don&#8217;t know how to change a tire, having the tools will allow a good samaritan to help you out.</p>
<h3>Make some friends</h3>
<p>The best way to start riding and stay riding is have friends that ride. Everyone needs motivation. If your friend is going on a ride it will help you to get out the door. It&#8217;ll be more fun and you&#8217;ll want to do it more. Riding by yourself can be very boring, especially really long rides. Additionally the slightest obstacle, cold, rain, wind, can be just enough for you to put off riding that day. If you have friends that say &#8220;who cares, let&#8217;s go anyway&#8221; you&#8217;ll forget about it because you don&#8217;t want to be the wimp, or let your friends down. Lastly the more the merrier. Riding in a group of two is fun. Riding in a group of 10 is fantastic!</p>
<h3>Conclusion</h3>
<p>These are just a few of the basics to get you started, hope they help. If you have any stories that you can relate let me know by commenting.</p>
]]></content:encoded>
			<wfw:commentRss>http://joelcory.com/blog/2007/11/02/how-to-buy-a-bicycle/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Everyone can do their part</title>
		<link>http://joelcory.com/blog/2007/10/15/everyone-can-do-their-part/</link>
		<comments>http://joelcory.com/blog/2007/10/15/everyone-can-do-their-part/#comments</comments>
		<pubDate>Mon, 15 Oct 2007 19:34:20 +0000</pubDate>
		<dc:creator>Joel Cory</dc:creator>
				<category><![CDATA[bad design]]></category>
		<category><![CDATA[blogging]]></category>
		<category><![CDATA[climate change]]></category>
		<category><![CDATA[environment]]></category>
		<category><![CDATA[good design]]></category>
		<category><![CDATA[Industrial Design]]></category>
		<category><![CDATA[reliability]]></category>

		<guid isPermaLink="false">http://joelcory.com/blog/2007/10/15/everyone-can-do-their-part/</guid>
		<description><![CDATA[Finally an excuse to rant about an environmental issue. Blog Action Day has asked that bloggers around the world call attention to the global issue that affects everyone, the environment. Here&#8217;s the details: Publish a post on their blog which relates to an issue of their own choice pertaining to the environment. For example: A [...]]]></description>
			<content:encoded><![CDATA[<p>Finally an excuse to rant about an environmental issue. <a href="http://blogactionday.org">Blog Action Day</a> has asked that bloggers around the world call attention to the global issue that affects everyone, the environment. Here&#8217;s the details:</p>
<p><code>Publish a post on their blog which relates to an issue of their own choice pertaining to the environment.</code></p>
<p><code>For example: A blog about money might write about how to save around the home by using environmentally friendly ideas. Similarly a blog about politics might examine what weight environmental policy holds in the political arena.</code></p>
<p>So here&#8217;s my take on what designers everywhere can do to help. <span id="more-55"></span></p>
<h3>Every little bit counts</h3>
<p>Save your money. This a simple step that everyone can get behind. I&#8217;m not saying to stop spending, but think twice before you buy. If the product you&#8217;re looking at is only going to be useful for a short time, or it&#8217;s an impulse purchase&#8230;maybe you don&#8217;t need it. As a designer I walk through the aisles of products and can&#8217;t help but think how many products out there are crap. Novelty items, poorly constructed, or just plain wasteful. Stop buying things that are so cheap that they will end up in the trash when they break in a month. Do you really need another gadget? Do your kids need a cheap, useless toy with their happy meal just because a new movie came out?</p>
<h3>Buy smarter</h3>
<p>Stop buying products that have better alternatives. No more incandescent bulbs, SUVs to commute to work in (or drop your kids off at school), and mass produced food. Compact fluorescent bulbs are getting cheaper everyday, and they save you money on your utility bills. SUVs are only necessary when you are taking more than five people, with cargo. How many times do you see single drivers in a 17mpg gas guzzler? What a waste, especially for the owner. If you don&#8217;t need the room why are you wasting your money? If more consumers stopped buying these beasts, maybe auto manufacturers would stop designing them. Most people don&#8217;t realize that mass produced food is actually costing them more than the fresher alternatives in the grocery store. If you are fighting weight problems diet soda is not helping you. Frozen dinners are not healthy even if they are from weight watchers. Fast food is the enemy.</p>
<h3>Green is good for business</h3>
<p>The economy couldn&#8217;t possibly be hurt by going green. Making smarter products that use less resources and are re-usable or recyclable costs more? Why? If something takes less resources to produce it should cost less. If you can reuse portions of the products at end-of-life for new products doesn&#8217;t that bring costs down? If oil and coal companies invested money into solar, wind, and hydro couldn&#8217;t they make just as much money in the long run? Why are we subsidizing ethanol, and corn for fuel when we could be offering these benefits to technologies that will improve mileage not degrade it? If a company made a product that would save you thousands of dollars on transportation costs annually by eliminating gas, filters, and oil changes wouldn&#8217;t you line up to buy it? Why couldn&#8217;t GM, Ford, and Chrysler make these products? </p>
<p>Going green can only hurt companies that can&#8217;t adapt to the changing market. Let&#8217;s help them on their way, whether that&#8217;s success or failure. We owe it to ourselves to design, buy, and lobby for products that help everyone, not just the people and companies that are already rich.</p>
]]></content:encoded>
			<wfw:commentRss>http://joelcory.com/blog/2007/10/15/everyone-can-do-their-part/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

