<?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/" version="2.0">

<channel>
	<title>Stopdesign</title>
	
	<link>http://stopdesign.com</link>
	<description>Stopdesign is the creative outlet of Douglas Bowman.</description>
	<pubDate>Tue, 09 Jun 2009 21:20:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://www.stopdesign.com/index.xml" type="application/rss+xml" /><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Fwww.stopdesign.com%2Findex.xml" src="http://us.i1.yimg.com/us.yimg.com/i/us/my/addtomyyahoo4.gif">Subscribe with My Yahoo!</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.newsgator.com/ngs/subscriber/subext.aspx?url=http%3A%2F%2Fwww.stopdesign.com%2Findex.xml" src="http://www.newsgator.com/images/ngsub1.gif">Subscribe with NewsGator</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://feeds.my.aol.com/add.jsp?url=http%3A%2F%2Fwww.stopdesign.com%2Findex.xml" src="http://o.aolcdn.com/favorites.my.aol.com/webmaster/ffclient/webroot/locale/en-US/images/myAOLButtonSmall.gif">Subscribe with My AOL</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.bloglines.com/sub/http://www.stopdesign.com/index.xml" src="http://www.bloglines.com/images/sub_modern11.gif">Subscribe with Bloglines</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Fwww.stopdesign.com%2Findex.xml" src="http://www.netvibes.com/img/add2netvibes.gif">Subscribe with Netvibes</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://fusion.google.com/add?feedurl=http%3A%2F%2Fwww.stopdesign.com%2Findex.xml" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.pageflakes.com/subscribe.aspx?url=http%3A%2F%2Fwww.stopdesign.com%2Findex.xml" src="http://www.pageflakes.com/ImageFile.ashx?instanceId=Static_4&amp;fileName=ATP_blu_91x17.gif">Subscribe with Pageflakes</feedburner:feedFlare><item>
		<title>A Deep Breath</title>
		<link>http://www.randsinrepose.com/archives/2009/06/01/a_deep_breath.html</link>
		<comments>http://stopdesign.com/archive/2009/06/01/a-deep-breath.html#comments</comments>
		<pubDate>Mon, 01 Jun 2009 16:38:48 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
		
		<category><![CDATA[links]]></category>

		<category><![CDATA[management]]></category>

		<category><![CDATA[stress]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/06/01/a-deep-breath.html</guid>
		<description>&lt;blockquote&gt;&lt;p&gt;You’re encouraging the random and random is how you’re going to win. Random is how you’re going to discover a path through a problem that no one else has found and that starts with breathing deeply.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Even though the subject matter and approach differs, this pairs nicely with an article on A List Apart last week: &lt;a href="http://www.alistapart.com/articles/burnout/"&gt;Burnout&lt;/a&gt;, by Scott Boms.&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;Your life should be just that—a life&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Good words, all around. &lt;/p&gt;
&lt;p&gt;-&lt;a href="http://stopdesign.com/archive/2009/06/01/a-deep-breath.html"&gt;archive link&lt;/a&gt;-&lt;/p&gt;</description>
			<content:encoded><![CDATA[<blockquote><p>You’re encouraging the random and random is how you’re going to win. Random is how you’re going to discover a path through a problem that no one else has found and that starts with breathing deeply.</p></blockquote>
<p>Even though the subject matter and approach differs, this pairs nicely with an article on A List Apart last week: <a href="http://www.alistapart.com/articles/burnout/">Burnout</a>, by Scott Boms.</p>
<blockquote><p>Your life should be just that—a life</p></blockquote>
<p>Good words, all around. </p>
<p>-<a href="http://stopdesign.com/archive/2009/06/01/a-deep-breath.html">archive link</a>-</p><img src="http://feeds.feedburner.com/~r/stopdesign/~4/sTTzPrUpRLo" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/06/01/a-deep-breath.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Introducing Typekit</title>
		<link>http://blog.typekit.com/2009/05/27/introducing-typekit/</link>
		<comments>http://stopdesign.com/archive/2009/05/28/introducing-typekit.html#comments</comments>
		<pubDate>Thu, 28 May 2009 16:42:51 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
		
		<category><![CDATA[links]]></category>

		<category><![CDATA[design]]></category>

		<category><![CDATA[typography]]></category>

		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/05/28/introducing-typekit.html</guid>
		<description>&lt;p&gt;Emphasis is my own&amp;#8230;&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;As a Typekit user, you’ll have access to our library of high-quality fonts. Just add a line of JavaScript to your markup, tell us what fonts you want to use, and then craft your pages the way you always have. Except now you’ll be able to use real fonts. &lt;strong&gt;This really is going to change web design.&lt;/strong&gt;&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Also worth checking out, Jeff posted a &lt;a href="http://www.flickr.com/photos/veen/3572372312/"&gt;preview of the Typekit home page&lt;/a&gt; yesterday. Looking forward to how this will change typography and design for the web. &lt;/p&gt;
&lt;p&gt;-&lt;a href="http://stopdesign.com/archive/2009/05/28/introducing-typekit.html"&gt;archive link&lt;/a&gt;-&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>Emphasis is my own&#8230;</p>
<blockquote><p>As a Typekit user, you’ll have access to our library of high-quality fonts. Just add a line of JavaScript to your markup, tell us what fonts you want to use, and then craft your pages the way you always have. Except now you’ll be able to use real fonts. <strong>This really is going to change web design.</strong></p></blockquote>
<p>Also worth checking out, Jeff posted a <a href="http://www.flickr.com/photos/veen/3572372312/">preview of the Typekit home page</a> yesterday. Looking forward to how this will change typography and design for the web. </p>
<p>-<a href="http://stopdesign.com/archive/2009/05/28/introducing-typekit.html">archive link</a>-</p><img src="http://feeds.feedburner.com/~r/stopdesign/~4/e5ynF0bhaQ0" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/05/28/introducing-typekit.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Universal Internet Explorer 6 CSS</title>
		<link>http://forabeautifulweb.com/blog/about/universal_internet_explorer_6_css</link>
		<comments>http://stopdesign.com/archive/2009/05/20/universal-internet-explorer-6-css.html#comments</comments>
		<pubDate>Thu, 21 May 2009 02:00:33 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
		
		<category><![CDATA[links]]></category>

		<category><![CDATA[browser]]></category>

		<category><![CDATA[css]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/05/20/universal-internet-explorer-6-css.html</guid>
		<description>&lt;p&gt;Mr. Clarke advocates creating one single universal style sheet to handle all styling in IE6, and to stop worrying about making content in IE6 look anything like the high-end experience.&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;I&amp;#8217;m now advocating to my clients (and to you), that where feasible, not to waste hours in time and a client&amp;#8217;s money on lengthy workarounds in an unnecessary attempt at cross-browser perfection. Instead, you and I should provide simple but effectively designed HTML elements. This means just great typography for headings, paragraphs, quotations, lists, tables and forms and no styling of layout.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;This will work well for content-focused web sites. And then maybe it&amp;#8217;s officially time to completely drop support of IE6 for web apps. &lt;/p&gt;
&lt;p&gt;-&lt;a href="http://stopdesign.com/archive/2009/05/20/universal-internet-explorer-6-css.html"&gt;archive link&lt;/a&gt;-&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>Mr. Clarke advocates creating one single universal style sheet to handle all styling in IE6, and to stop worrying about making content in IE6 look anything like the high-end experience.</p>
<blockquote><p>I&#8217;m now advocating to my clients (and to you), that where feasible, not to waste hours in time and a client&#8217;s money on lengthy workarounds in an unnecessary attempt at cross-browser perfection. Instead, you and I should provide simple but effectively designed HTML elements. This means just great typography for headings, paragraphs, quotations, lists, tables and forms and no styling of layout.</p></blockquote>
<p>This will work well for content-focused web sites. And then maybe it&#8217;s officially time to completely drop support of IE6 for web apps. </p>
<p>-<a href="http://stopdesign.com/archive/2009/05/20/universal-internet-explorer-6-css.html">archive link</a>-</p><img src="http://feeds.feedburner.com/~r/stopdesign/~4/bajiJWgMoAc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/05/20/universal-internet-explorer-6-css.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Welcome, Wired. We call this land “Internet”</title>
		<link>http://gadgets.boingboing.net/2009/05/18/welcome-wired-we-cal.html</link>
		<comments>http://stopdesign.com/archive/2009/05/19/welcome-wired-we-call-this-land-internet.html#comments</comments>
		<pubDate>Tue, 19 May 2009 19:00:34 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
		
		<category><![CDATA[links]]></category>

		<category><![CDATA[wired]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/05/19/welcome-wired-we-call-this-land-internet.html</guid>
		<description>&lt;p&gt;Interesting take on the future of &lt;cite&gt;Wired&lt;/cite&gt; (mag vs. website).&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;Wired is great print, but if the magazine can&amp;#8217;t make money and is shuttered, taking the website down with it, I&amp;#8217;m going to be livid. Not that making money online is easy—it&amp;#8217;s not, especially without sacrificing your ethics and your voice—but if any mainstream outlet should be able to make the transition, it should be Wired.&lt;/p&gt;
&lt;p&gt;I fear that may be impossible, not just for Wired but for all these old brands, because they can&amp;#8217;t accept that the work at which they have excelled for years will be just as important when it&amp;#8217;s online—and online only.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Reading though the comments provides an even more interesting story and a broader perspective. Comments by several former and current Wiredlings, including a few responses by Chris Anderson who passes blame to corporate (Conde Nast) decision-making. &lt;/p&gt;
&lt;p&gt;-&lt;a href="http://stopdesign.com/archive/2009/05/19/welcome-wired-we-call-this-land-internet.html"&gt;archive link&lt;/a&gt;-&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>Interesting take on the future of <cite>Wired</cite> (mag vs. website).</p>
<blockquote><p>Wired is great print, but if the magazine can&#8217;t make money and is shuttered, taking the website down with it, I&#8217;m going to be livid. Not that making money online is easy—it&#8217;s not, especially without sacrificing your ethics and your voice—but if any mainstream outlet should be able to make the transition, it should be Wired.</p>
<p>I fear that may be impossible, not just for Wired but for all these old brands, because they can&#8217;t accept that the work at which they have excelled for years will be just as important when it&#8217;s online—and online only.</p></blockquote>
<p>Reading though the comments provides an even more interesting story and a broader perspective. Comments by several former and current Wiredlings, including a few responses by Chris Anderson who passes blame to corporate (Conde Nast) decision-making. </p>
<p>-<a href="http://stopdesign.com/archive/2009/05/19/welcome-wired-we-call-this-land-internet.html">archive link</a>-</p><img src="http://feeds.feedburner.com/~r/stopdesign/~4/K594BaOqbIM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/05/19/welcome-wired-we-call-this-land-internet.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Great Designs Should Be Experienced and Not Seen</title>
		<link>http://www.uie.com/articles/experiencedesign</link>
		<comments>http://stopdesign.com/archive/2009/05/14/great-designs-should-be-experienced-and-not-seen.html#comments</comments>
		<pubDate>Thu, 14 May 2009 22:00:14 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
		
		<category><![CDATA[links]]></category>

		<category><![CDATA[design]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/05/14/great-designs-should-be-experienced-and-not-seen.html</guid>
		<description>&lt;p&gt;The best design is that which does its job and stays out of the way. Jared Spool on invisible design:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;While all these things are what the designers at Netflix work hard on every day, they go unmentioned by their customers. It&amp;#39;s not because these aspects aren&amp;#39;t important. It&amp;#39;s because the designers have done their job really well: they&amp;#39;ve made them invisible.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;-&lt;a href="http://stopdesign.com/archive/2009/05/14/great-designs-should-be-experienced-and-not-seen.html"&gt;archive link&lt;/a&gt;-&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>The best design is that which does its job and stays out of the way. Jared Spool on invisible design:</p>
<blockquote><p>While all these things are what the designers at Netflix work hard on every day, they go unmentioned by their customers. It&#39;s not because these aspects aren&#39;t important. It&#39;s because the designers have done their job really well: they&#39;ve made them invisible.</p></blockquote>
<p>-<a href="http://stopdesign.com/archive/2009/05/14/great-designs-should-be-experienced-and-not-seen.html">archive link</a>-</p><img src="http://feeds.feedburner.com/~r/stopdesign/~4/uQdwTWhXkGM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/05/14/great-designs-should-be-experienced-and-not-seen.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Choices</title>
		<link>http://furbo.org/2008/12/02/choices/</link>
		<comments>http://stopdesign.com/archive/2009/05/08/choices.html#comments</comments>
		<pubDate>Fri, 08 May 2009 17:21:29 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
		
		<category><![CDATA[links]]></category>

		<category><![CDATA[apps]]></category>

		<category><![CDATA[design]]></category>

		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/05/08/choices.html</guid>
		<description>&lt;p&gt;Craig directed me to this piece today after I complimented him on the new version of Twitterrific for the iPhone, stating how much I love seeing different approaches to Twitter client design. I hadn&amp;#8217;t seen his post (from December 2008) before today, but it&amp;#8217;s a good read that gives insight into some of the decisions behind Twitteriffic&amp;#8217;s design that are still applicable now.&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;Personally, I welcome this competition. Seeing the work of other developers whose work I respect and admire acts as an inspiration. Looking at how other developers tackle a problem domain often adds insight into solving similar issues with my own code. In other cases, it shows me how I don’t want to implement a feature (without the need to prototype.) In short, competition will make &lt;a href="http://iconfactory.com/twitterrific"&gt;Twitterrific&lt;/a&gt; better.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;-&lt;a href="http://stopdesign.com/archive/2009/05/08/choices.html"&gt;archive link&lt;/a&gt;-&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>Craig directed me to this piece today after I complimented him on the new version of Twitterrific for the iPhone, stating how much I love seeing different approaches to Twitter client design. I hadn&#8217;t seen his post (from December 2008) before today, but it&#8217;s a good read that gives insight into some of the decisions behind Twitteriffic&#8217;s design that are still applicable now.</p>
<blockquote><p>Personally, I welcome this competition. Seeing the work of other developers whose work I respect and admire acts as an inspiration. Looking at how other developers tackle a problem domain often adds insight into solving similar issues with my own code. In other cases, it shows me how I don’t want to implement a feature (without the need to prototype.) In short, competition will make <a href="http://iconfactory.com/twitterrific">Twitterrific</a> better.</p></blockquote>
<p>-<a href="http://stopdesign.com/archive/2009/05/08/choices.html">archive link</a>-</p><img src="http://feeds.feedburner.com/~r/stopdesign/~4/n8DeHH6M5RM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/05/08/choices.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Time to move beyond 960?</title>
		<link>http://cameronmoll.com/archives/2009/04/is_it_time_to_move_beyond_960/</link>
		<comments>http://stopdesign.com/archive/2009/04/23/time-to-move-beyond-960.html#comments</comments>
		<pubDate>Thu, 23 Apr 2009 21:36:12 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
		
		<category><![CDATA[links]]></category>

		<category><![CDATA[design]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/04/23/time-to-move-beyond-960.html</guid>
		<description>&lt;p&gt;Cameron asks the inevitable question about width on the Web. Probably not time yet for mainstream. But for showcases of design, why not start experimenting with the new real estate? &lt;/p&gt;
&lt;p&gt;-&lt;a href="http://stopdesign.com/archive/2009/04/23/time-to-move-beyond-960.html"&gt;archive link&lt;/a&gt;-&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>Cameron asks the inevitable question about width on the Web. Probably not time yet for mainstream. But for showcases of design, why not start experimenting with the new real estate? </p>
<p>-<a href="http://stopdesign.com/archive/2009/04/23/time-to-move-beyond-960.html">archive link</a>-</p><img src="http://feeds.feedburner.com/~r/stopdesign/~4/V60jdVZ6ZUM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/04/23/time-to-move-beyond-960.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Tal Leming on Web Fonts</title>
		<link>http://talleming.com/2009/04/21/web-fonts/</link>
		<comments>http://stopdesign.com/archive/2009/04/22/tal-leming-on-web-fonts.html#comments</comments>
		<pubDate>Wed, 22 Apr 2009 17:56:32 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
		
		<category><![CDATA[links]]></category>

		<category><![CDATA[type]]></category>

		<category><![CDATA[typography]]></category>

		<category><![CDATA[webfonts]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/04/22/tal-leming-on-web-fonts.html</guid>
		<description>&lt;p&gt;Seemingly reasonable middle-ground suggestions here that would allow web typography to move forward, allow people to use all the free fonts they want, yet continue to allow type designers to earn a living. &lt;/p&gt;
&lt;p&gt;-&lt;a href="http://stopdesign.com/archive/2009/04/22/tal-leming-on-web-fonts.html"&gt;archive link&lt;/a&gt;-&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>Seemingly reasonable middle-ground suggestions here that would allow web typography to move forward, allow people to use all the free fonts they want, yet continue to allow type designers to earn a living. </p>
<p>-<a href="http://stopdesign.com/archive/2009/04/22/tal-leming-on-web-fonts.html">archive link</a>-</p><img src="http://feeds.feedburner.com/~r/stopdesign/~4/tiM2SW1g7EQ" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/04/22/tal-leming-on-web-fonts.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>In Defense of Eye Candy</title>
		<link>http://www.alistapart.com/articles/indefenseofeyecandy</link>
		<comments>http://stopdesign.com/archive/2009/04/22/in-defense-of-eye-candy.html#comments</comments>
		<pubDate>Wed, 22 Apr 2009 17:42:35 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
		
		<category><![CDATA[links]]></category>

		<category><![CDATA[beauty]]></category>

		<category><![CDATA[design]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/04/22/in-defense-of-eye-candy.html</guid>
		<description>&lt;p&gt;Stephen Anderson:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;The more we learn about people, and how our brains process information, the more we learn the truth of that phrase: form and function aren’t separate items. If we believe that style somehow exists independent of functionality, that we can treat aesthetics and function as two separate pieces, then we ignore the evidence that beauty is much more than decoration. Our brains can’t help but agree.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Can&amp;#8217;t say that I agree with all the examples he used. But important points that stand on their own, nonetheless. &lt;/p&gt;
&lt;p&gt;-&lt;a href="http://stopdesign.com/archive/2009/04/22/in-defense-of-eye-candy.html"&gt;archive link&lt;/a&gt;-&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>Stephen Anderson:</p>
<blockquote><p>The more we learn about people, and how our brains process information, the more we learn the truth of that phrase: form and function aren’t separate items. If we believe that style somehow exists independent of functionality, that we can treat aesthetics and function as two separate pieces, then we ignore the evidence that beauty is much more than decoration. Our brains can’t help but agree.</p></blockquote>
<p>Can&#8217;t say that I agree with all the examples he used. But important points that stand on their own, nonetheless. </p>
<p>-<a href="http://stopdesign.com/archive/2009/04/22/in-defense-of-eye-candy.html">archive link</a>-</p><img src="http://feeds.feedburner.com/~r/stopdesign/~4/PWnn5bOFOOQ" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/04/22/in-defense-of-eye-candy.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Fluid Images</title>
		<link>http://unstoppablerobotninja.com/entry/fluid-images/</link>
		<comments>http://stopdesign.com/archive/2009/04/17/fluid-images.html#comments</comments>
		<pubDate>Sat, 18 Apr 2009 01:00:03 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
		
		<category><![CDATA[links]]></category>

		<category><![CDATA[css]]></category>

		<category><![CDATA[tips]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/04/17/fluid-images.html</guid>
		<description>&lt;p&gt;Nice going, Ethan. Definitely one to keep in the ol&amp;#8217; bag o&amp;#8217; tricks. &lt;/p&gt;
&lt;p&gt;-&lt;a href="http://stopdesign.com/archive/2009/04/17/fluid-images.html"&gt;archive link&lt;/a&gt;-&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>Nice going, Ethan. Definitely one to keep in the ol&#8217; bag o&#8217; tricks. </p>
<p>-<a href="http://stopdesign.com/archive/2009/04/17/fluid-images.html">archive link</a>-</p><img src="http://feeds.feedburner.com/~r/stopdesign/~4/7Ay5E1fYLZY" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/04/17/fluid-images.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Apple notebook packaging comparison</title>
		<link>http://stopdesign.com/archive/2009/04/12/apple-packaging.html</link>
		<comments>http://stopdesign.com/archive/2009/04/12/apple-packaging.html#comments</comments>
		<pubDate>Mon, 13 Apr 2009 05:54:01 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
		
		<category><![CDATA[entries]]></category>

		<category><![CDATA[apple]]></category>

		<category><![CDATA[packaging]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/04/12/apple-notebook-packaging-comparison.html</guid>
		<description>&lt;p&gt;Interesting comparison (my own) of packaging for Apple notebooks. I&amp;#8217;ve been noticing a trend over the last few years to cut way down on box size for both hardware and software. But I still think it&amp;#8217;s interesting to see side-by-side comparisons for similar items over time. This &lt;a href="http://www.flickr.com/photos/stop/3437277676/"&gt;first photo&lt;/a&gt; shows the original box for a 12&amp;quot; PowerBook G4 purchased in 2004 (black box) next to the box for the current generation 15&amp;quot; MacBook Pro (white box) purchased in 2009.&lt;/p&gt;
&lt;p&gt;Another &lt;a href="http://www.flickr.com/photos/stop/3436482831/"&gt;similar photo&lt;/a&gt; compares packaging for the 12&amp;quot; iBook purchased in 2006 next to the box for the current 13&amp;quot; white MacBook purchased in 2009.&lt;/p&gt;
&lt;p&gt;In both cases, the newer notebook is &lt;strong&gt;larger&lt;/strong&gt; than the older notebook, yet still uses a much &lt;strong&gt;smaller&lt;/strong&gt; box.&lt;/p&gt;
&lt;p&gt;After recent Unboxings&amp;trade; of the MB and MBP, I noted there&amp;#8217;s no less &amp;#8220;stuff&amp;#8221; in the box as far as hardware, adapters, install discs, and printed material. The new packaging designs just forgo the thick molded styrofoam padding of the old boxes.&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>Interesting comparison (my own) of packaging for Apple notebooks. I&#8217;ve been noticing a trend over the last few years to cut way down on box size for both hardware and software. But I still think it&#8217;s interesting to see side-by-side comparisons for similar items over time. This <a href="http://www.flickr.com/photos/stop/3437277676/">first photo</a> shows the original box for a 12&quot; PowerBook G4 purchased in 2004 (black box) next to the box for the current generation 15&quot; MacBook Pro (white box) purchased in 2009.</p>
<p>Another <a href="http://www.flickr.com/photos/stop/3436482831/">similar photo</a> compares packaging for the 12&quot; iBook purchased in 2006 next to the box for the current 13&quot; white MacBook purchased in 2009.</p>
<p>In both cases, the newer notebook is <strong>larger</strong> than the older notebook, yet still uses a much <strong>smaller</strong> box.</p>
<p>After recent Unboxings&trade; of the MB and MBP, I noted there&#8217;s no less &#8220;stuff&#8221; in the box as far as hardware, adapters, install discs, and printed material. The new packaging designs just forgo the thick molded styrofoam padding of the old boxes.</p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/64gZW6-Bu5U" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/04/12/apple-packaging.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Attribution and Affiliation on All Things Digital</title>
		<link>http://waxy.org/2009/04/all_things_digital_and_transparency_in_online_journalism/</link>
		<comments>http://stopdesign.com/archive/2009/04/09/attribution-and-affiliation-on-all-things-digital.html#comments</comments>
		<pubDate>Thu, 09 Apr 2009 16:27:25 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
		
		<category><![CDATA[links]]></category>

		<category><![CDATA[attribution]]></category>

		<category><![CDATA[content]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/04/09/attribution-and-affiliation-on-all-things-digital.html</guid>
		<description>&lt;p&gt;Andy Baio digs into the reuse of certain content by AllThingsD for their &lt;a href="http://voices.allthingsd.com/"&gt;Voices&lt;/a&gt; section:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;Ultimately, if authors are happy, there&amp;#8217;s no problem. But it seems like there&amp;#8217;s a divide between two types of writers online: unaffiliated independent bloggers running their own sites and bloggers employed by larger online magazines.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Also, be sure to read the &lt;a href="http://dashes.com/anil/2009/04/fair-use-for-fair-people.html"&gt;related response from Anil Dash&lt;/a&gt; about how the Associated Press plans to handle a similar reuse of content:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;If the Associated Press made its argument on the basis of credibility and reputation, transparency and accountability, as the web-native publishers have, it would be far easier to defend their desire to share in the business model developed by the aggregators.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;-&lt;a href="http://stopdesign.com/archive/2009/04/09/attribution-and-affiliation-on-all-things-digital.html"&gt;archive link&lt;/a&gt;-&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>Andy Baio digs into the reuse of certain content by AllThingsD for their <a href="http://voices.allthingsd.com/">Voices</a> section:</p>
<blockquote><p>Ultimately, if authors are happy, there&#8217;s no problem. But it seems like there&#8217;s a divide between two types of writers online: unaffiliated independent bloggers running their own sites and bloggers employed by larger online magazines.</p></blockquote>
<p>Also, be sure to read the <a href="http://dashes.com/anil/2009/04/fair-use-for-fair-people.html">related response from Anil Dash</a> about how the Associated Press plans to handle a similar reuse of content:</p>
<blockquote><p>If the Associated Press made its argument on the basis of credibility and reputation, transparency and accountability, as the web-native publishers have, it would be far easier to defend their desire to share in the business model developed by the aggregators.</p></blockquote>
<p>-<a href="http://stopdesign.com/archive/2009/04/09/attribution-and-affiliation-on-all-things-digital.html">archive link</a>-</p><img src="http://feeds.feedburner.com/~r/stopdesign/~4/DLBh_R6EfeM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/04/09/attribution-and-affiliation-on-all-things-digital.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Cufón</title>
		<link>http://wiki.github.com/sorccu/cufon/about</link>
		<comments>http://stopdesign.com/archive/2009/04/08/cufn.html#comments</comments>
		<pubDate>Wed, 08 Apr 2009 16:07:33 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
		
		<category><![CDATA[links]]></category>

		<category><![CDATA[design]]></category>

		<category><![CDATA[tools]]></category>

		<category><![CDATA[typography]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/04/08/cufn.html</guid>
		<description>&lt;blockquote&gt;&lt;p&gt;Fast text replacement with canvas and VML - no Flash or images required.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Oooh. Must experiment with this soon. (via &lt;a href="http://twitter.com/Hicksdesign/status/1476579650"&gt;@hicksdesign&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;-&lt;a href="http://stopdesign.com/archive/2009/04/08/cufn.html"&gt;archive link&lt;/a&gt;-&lt;/p&gt;</description>
			<content:encoded><![CDATA[<blockquote><p>Fast text replacement with canvas and VML - no Flash or images required.</p></blockquote>
<p>Oooh. Must experiment with this soon. (via <a href="http://twitter.com/Hicksdesign/status/1476579650">@hicksdesign</a>)</p>
<p>-<a href="http://stopdesign.com/archive/2009/04/08/cufn.html">archive link</a>-</p><img src="http://feeds.feedburner.com/~r/stopdesign/~4/vmmv2sj4nfI" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/04/08/cufn.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Adobe’s plugin for Photoshop CS4 to disable canvas rotation via the trackpad</title>
		<link>http://www.adobe.com/support/downloads/detail.jsp?ftpID=4337</link>
		<comments>http://stopdesign.com/archive/2009/04/04/adobes-plugin-for-photoshop-cs4-to-disable-canvas-rotation-via-the-trackpad.html#comments</comments>
		<pubDate>Sun, 05 Apr 2009 00:00:08 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
		
		<category><![CDATA[links]]></category>

		<category><![CDATA[adobe]]></category>

		<category><![CDATA[software]]></category>

		<category><![CDATA[tips]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/04/04/adobes-plugin-for-photoshop-cs4-to-disable-canvas-rotation-via-the-trackpad.html</guid>
		<description>&lt;p&gt;I&amp;#8217;m linking to this because I&amp;#8217;ve been stung by the problem too. The issue is with new MacBooks and MacBook Pros with the button-less trackpad. These trackpads have no dead zone like the old trackpads did. So until I get accustomed to using them, I often end up resting my right thumb on the lower portion of the trackpad where the physical button used to be. Because of this, once I go to move the cursor with the trackpad, I inadvertently perform a two-finger gesture, which Apple now recognizes on these new trackpads. Photoshop interprets these as either zoom or rotate actions, which is rarely what I want to happen. This plugin disables those actions in Photoshop, until Adobe engineers figure a graceful way to interpret (or otherwise ignore) two-finger gestures. &lt;/p&gt;
&lt;p&gt;-&lt;a href="http://stopdesign.com/archive/2009/04/04/adobes-plugin-for-photoshop-cs4-to-disable-canvas-rotation-via-the-trackpad.html"&gt;archive link&lt;/a&gt;-&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>I&#8217;m linking to this because I&#8217;ve been stung by the problem too. The issue is with new MacBooks and MacBook Pros with the button-less trackpad. These trackpads have no dead zone like the old trackpads did. So until I get accustomed to using them, I often end up resting my right thumb on the lower portion of the trackpad where the physical button used to be. Because of this, once I go to move the cursor with the trackpad, I inadvertently perform a two-finger gesture, which Apple now recognizes on these new trackpads. Photoshop interprets these as either zoom or rotate actions, which is rarely what I want to happen. This plugin disables those actions in Photoshop, until Adobe engineers figure a graceful way to interpret (or otherwise ignore) two-finger gestures. </p>
<p>-<a href="http://stopdesign.com/archive/2009/04/04/adobes-plugin-for-photoshop-cs4-to-disable-canvas-rotation-via-the-trackpad.html">archive link</a>-</p><img src="http://feeds.feedburner.com/~r/stopdesign/~4/cMVHfGchuYE" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/04/04/adobes-plugin-for-photoshop-cs4-to-disable-canvas-rotation-via-the-trackpad.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Hello, Twitter</title>
		<link>http://stopdesign.com/archive/2009/03/31/hello-twitter.html</link>
		<comments>http://stopdesign.com/archive/2009/03/31/hello-twitter.html#comments</comments>
		<pubDate>Tue, 31 Mar 2009 20:57:53 +0000</pubDate>
		<dc:creator>twitter</dc:creator>
		
		<category><![CDATA[entries]]></category>

		<category><![CDATA[design]]></category>

		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://stopdesign.com/?p=2139</guid>
		<description>&lt;p&gt;Part 2 of 2 (here&amp;#8217;s &lt;a href="http://stopdesign.com/archive/2009/03/20/goodbye-google.html"&gt;Part 1&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;Yesterday was my first day @twitter.&lt;/p&gt;
&lt;p&gt;Yes, it&amp;#8217;s true. After reading a bit of speculation over the past few weeks, I&amp;#8217;ll confirm here that I am, indeed, joining Twitter. I don&amp;#8217;t remember ever being as eager or excited to start a new job as I&amp;#8217;ve been with this one. (Thus, why I only took one week off between jobs.)&lt;span id="more-2139"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Over the past year, I spoke with several organizations about coming on board to lead a design team. But Twitter felt the like most natural fit from the very start of my talks with the team. It&amp;#8217;s still early in Twitter&amp;#8217;s history. The company is small. Its user base is growing rapidly. And I see lots of potential to directly impact and to help shape the Twitter brand.&lt;/p&gt;
&lt;p&gt;Add to that the fact that I know, understand, and respect the company&amp;#8217;s leadership. And they know and respect my work, capabilities, and philosophy. (Several of us worked together on the &lt;a href="http://stopdesign.com/archive/2004/05/09/blogger.html"&gt;redesign of Blogger&lt;/a&gt; in 2004.) A better fit is hard to find.&lt;/p&gt;
&lt;p&gt;As Creative Director, I&amp;#8217;ll have a few obvious responsibilities. Like building and shaping a design team, overseeing an evolving set of design challenges for a growing list of features and uses, and contributing to the company&amp;#8217;s overall design strategy. Other responsibilities will include taking advantage of Twitter (and other means) to collect feedback and ideas about new features, implementations, or general UI changes.&lt;/p&gt;
&lt;p&gt;I recognize the task before us is not small nor easy. Twitter means different things for different people and organizations, and it gets used in so many different ways. Maintaining the simplicity of the service is critical. At the same time, so is supporting an expanding set of features that enable new ways for users to connect with real-time information from sources that interest them.&lt;/p&gt;
&lt;p&gt;Despite the changes ahead, I don&amp;#8217;t regret my decision. Sure, I left a 20,000-person company with billions of dollars in revenue to join a startup with just over 30 employees and venture capital in the bank. The shift means I need to adjust to the pace at which we move, the scope of responsibility for each employee, and expectations for available resources. It means significant changes to how we, as a company, approach problems and propose solutions. And it also means more time for me back in San Francisco. In fact, from my desk, I can look out at the old Wired building where I got my start on the web thirteen years ago. I welcome changes like this with open arms.&lt;/p&gt;
&lt;p&gt;Here&amp;#8217;s to new challenges and new opportunities. Even when they&amp;#8217;re taken on, one hundred and forty characters at a time.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update:&lt;/strong&gt; Here&amp;#8217;s &lt;a href="http://blog.twitter.com/2009/03/welcome-doug-bowman.html"&gt;Twitter&amp;#8217;s announcement&lt;/a&gt; on the blog.&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>Part 2 of 2 (here&#8217;s <a href="http://stopdesign.com/archive/2009/03/20/goodbye-google.html">Part 1</a>)</p>
<p>Yesterday was my first day @twitter.</p>
<p>Yes, it&#8217;s true. After reading a bit of speculation over the past few weeks, I&#8217;ll confirm here that I am, indeed, joining Twitter. I don&#8217;t remember ever being as eager or excited to start a new job as I&#8217;ve been with this one. (Thus, why I only took one week off between jobs.)<span id="more-2139"></span></p>
<p>Over the past year, I spoke with several organizations about coming on board to lead a design team. But Twitter felt the like most natural fit from the very start of my talks with the team. It&#8217;s still early in Twitter&#8217;s history. The company is small. Its user base is growing rapidly. And I see lots of potential to directly impact and to help shape the Twitter brand.</p>
<p>Add to that the fact that I know, understand, and respect the company&#8217;s leadership. And they know and respect my work, capabilities, and philosophy. (Several of us worked together on the <a href="http://stopdesign.com/archive/2004/05/09/blogger.html">redesign of Blogger</a> in 2004.) A better fit is hard to find.</p>
<p>As Creative Director, I&#8217;ll have a few obvious responsibilities. Like building and shaping a design team, overseeing an evolving set of design challenges for a growing list of features and uses, and contributing to the company&#8217;s overall design strategy. Other responsibilities will include taking advantage of Twitter (and other means) to collect feedback and ideas about new features, implementations, or general UI changes.</p>
<p>I recognize the task before us is not small nor easy. Twitter means different things for different people and organizations, and it gets used in so many different ways. Maintaining the simplicity of the service is critical. At the same time, so is supporting an expanding set of features that enable new ways for users to connect with real-time information from sources that interest them.</p>
<p>Despite the changes ahead, I don&#8217;t regret my decision. Sure, I left a 20,000-person company with billions of dollars in revenue to join a startup with just over 30 employees and venture capital in the bank. The shift means I need to adjust to the pace at which we move, the scope of responsibility for each employee, and expectations for available resources. It means significant changes to how we, as a company, approach problems and propose solutions. And it also means more time for me back in San Francisco. In fact, from my desk, I can look out at the old Wired building where I got my start on the web thirteen years ago. I welcome changes like this with open arms.</p>
<p>Here&#8217;s to new challenges and new opportunities. Even when they&#8217;re taken on, one hundred and forty characters at a time.</p>
<p><strong>Update:</strong> Here&#8217;s <a href="http://blog.twitter.com/2009/03/welcome-doug-bowman.html">Twitter&#8217;s announcement</a> on the blog.</p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/3O2Jg0WLZ9c" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/03/31/hello-twitter.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Goodbye, Google</title>
		<link>http://stopdesign.com/archive/2009/03/20/goodbye-google.html</link>
		<comments>http://stopdesign.com/archive/2009/03/20/goodbye-google.html#comments</comments>
		<pubDate>Fri, 20 Mar 2009 14:28:11 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
		
		<category><![CDATA[entries]]></category>

		<category><![CDATA[design]]></category>

		<category><![CDATA[google]]></category>

		<guid isPermaLink="false">http://stopdesign.com/?p=2111</guid>
		<description>&lt;p&gt;Part 1 of 2 (here&amp;#8217;s &lt;a href="http://stopdesign.com/archive/2009/03/31/hello-twitter.html"&gt;Part 2&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;Today is my last day at Google.&lt;/p&gt;
&lt;p&gt;I started working in-house at Google &lt;a href="http://stopdesign.com/archive/2006/05/27/going-to-google.html"&gt;almost three years ago&lt;/a&gt;. I built a team from scratch. I was fortunate to hire a team of a very talented designers. We introduced Visual Design as a discipline to Google. And we produced amazing work together. I&amp;#8217;m very proud of my team, and I wish them well. They have a lot of challenging work ahead. But for me, it&amp;#8217;s time to move on.&lt;span id="more-2111"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Do I have something else lined up? Yes. That will be covered in Part 2. So I&amp;#8217;m not leaving just to leave. But I&amp;#8217;m not going to sugarcoat the reasons for my departure either. The scale at which Google operates was an early attractor for me. Potential to impact millions of people? Where do I sign? Unfortunately for me, there was one small problem I didn&amp;#8217;t see back then.&lt;/p&gt;
&lt;p&gt;When I joined Google as its first visual designer, the company was already seven years old. Seven years is a long time to run a company without a classically trained designer. Google had plenty of designers on staff then, but most of them had backgrounds in CS or HCI. And none of them were in high-up, respected leadership positions. Without a person at (or near) the helm who thoroughly understands the &lt;a href="http://en.wikipedia.org/wiki/Design_principles_and_elements"&gt;principles and elements of Design&lt;/a&gt;, a company eventually runs out of reasons for design decisions. With every new design decision, critics cry foul. Without conviction, doubt creeps in. Instincts fail. &amp;#8220;Is this the right move?&amp;#8221; When a company is filled with engineers, it turns to engineering to solve problems. Reduce each decision to a simple logic problem. Remove all subjectivity and just look at the data. Data in your favor? Ok, launch it. Data shows negative effects? Back to the drawing board. And that data eventually becomes a crutch for every decision, paralyzing the company and preventing it from making any daring design decisions.&lt;/p&gt;
&lt;p&gt;Yes, it&amp;#8217;s true that a team at Google couldn&amp;#8217;t decide between two blues, so they&amp;#8217;re &lt;a href="http://www.nytimes.com/2009/03/01/business/01marissa.html?pagewanted=print"&gt;testing 41 shades between each blue&lt;/a&gt; to see which one performs better. I had a recent debate over whether a border should be 3, 4 or 5 pixels wide, and was asked to prove my case. I can&amp;#8217;t operate in an environment like that. I&amp;#8217;ve grown tired of debating such minuscule design decisions. There are more exciting design problems in this world to tackle.&lt;/p&gt;
&lt;p&gt;I can&amp;#8217;t fault Google for this reliance on data. And I can&amp;#8217;t exactly point to financial failure or a shrinking number of users to prove it has done anything wrong. Billions of shareholder dollars are at stake. The company has millions of users around the world to please. That&amp;#8217;s no easy task. Google has momentum, and its leadership found a path that works very well. When I joined, I thought there was potential to help the company change course in its design direction. But I learned that Google had set its course long before I arrived. Google was a massive aircraft carrier, and I was just a small dinghy trying to push it a few degrees North.&lt;/p&gt;
&lt;p&gt;I&amp;#8217;m thankful for the opportunity I had to work at Google. I learned more than I thought I would. I&amp;#8217;ll miss the free food. I&amp;#8217;ll miss the occasional massage. I&amp;#8217;ll miss the authors, politicians, and celebrities that come to speak or perform. I&amp;#8217;ll miss early chances to play with cool toys before they&amp;#8217;re released to the public. Most of all, I&amp;#8217;ll miss working with the incredibly smart and talented people I got to know there. But I won&amp;#8217;t miss a design philosophy that lives or dies strictly by the sword of data.&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>Part 1 of 2 (here&#8217;s <a href="http://stopdesign.com/archive/2009/03/31/hello-twitter.html">Part 2</a>)</p>
<p>Today is my last day at Google.</p>
<p>I started working in-house at Google <a href="http://stopdesign.com/archive/2006/05/27/going-to-google.html">almost three years ago</a>. I built a team from scratch. I was fortunate to hire a team of a very talented designers. We introduced Visual Design as a discipline to Google. And we produced amazing work together. I&#8217;m very proud of my team, and I wish them well. They have a lot of challenging work ahead. But for me, it&#8217;s time to move on.<span id="more-2111"></span></p>
<p>Do I have something else lined up? Yes. That will be covered in Part 2. So I&#8217;m not leaving just to leave. But I&#8217;m not going to sugarcoat the reasons for my departure either. The scale at which Google operates was an early attractor for me. Potential to impact millions of people? Where do I sign? Unfortunately for me, there was one small problem I didn&#8217;t see back then.</p>
<p>When I joined Google as its first visual designer, the company was already seven years old. Seven years is a long time to run a company without a classically trained designer. Google had plenty of designers on staff then, but most of them had backgrounds in CS or HCI. And none of them were in high-up, respected leadership positions. Without a person at (or near) the helm who thoroughly understands the <a href="http://en.wikipedia.org/wiki/Design_principles_and_elements">principles and elements of Design</a>, a company eventually runs out of reasons for design decisions. With every new design decision, critics cry foul. Without conviction, doubt creeps in. Instincts fail. &#8220;Is this the right move?&#8221; When a company is filled with engineers, it turns to engineering to solve problems. Reduce each decision to a simple logic problem. Remove all subjectivity and just look at the data. Data in your favor? Ok, launch it. Data shows negative effects? Back to the drawing board. And that data eventually becomes a crutch for every decision, paralyzing the company and preventing it from making any daring design decisions.</p>
<p>Yes, it&#8217;s true that a team at Google couldn&#8217;t decide between two blues, so they&#8217;re <a href="http://www.nytimes.com/2009/03/01/business/01marissa.html?pagewanted=print">testing 41 shades between each blue</a> to see which one performs better. I had a recent debate over whether a border should be 3, 4 or 5 pixels wide, and was asked to prove my case. I can&#8217;t operate in an environment like that. I&#8217;ve grown tired of debating such minuscule design decisions. There are more exciting design problems in this world to tackle.</p>
<p>I can&#8217;t fault Google for this reliance on data. And I can&#8217;t exactly point to financial failure or a shrinking number of users to prove it has done anything wrong. Billions of shareholder dollars are at stake. The company has millions of users around the world to please. That&#8217;s no easy task. Google has momentum, and its leadership found a path that works very well. When I joined, I thought there was potential to help the company change course in its design direction. But I learned that Google had set its course long before I arrived. Google was a massive aircraft carrier, and I was just a small dinghy trying to push it a few degrees North.</p>
<p>I&#8217;m thankful for the opportunity I had to work at Google. I learned more than I thought I would. I&#8217;ll miss the free food. I&#8217;ll miss the occasional massage. I&#8217;ll miss the authors, politicians, and celebrities that come to speak or perform. I&#8217;ll miss early chances to play with cool toys before they&#8217;re released to the public. Most of all, I&#8217;ll miss working with the incredibly smart and talented people I got to know there. But I won&#8217;t miss a design philosophy that lives or dies strictly by the sword of data.</p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/75EVzGj0dG8" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/03/20/goodbye-google.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Bring Down IE 6</title>
		<link>http://www.bringdownie6.com/</link>
		<comments>http://stopdesign.com/archive/2009/03/16/bring-down-ie-6.html#comments</comments>
		<pubDate>Mon, 16 Mar 2009 16:28:26 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
		
		<category><![CDATA[links]]></category>

		<category><![CDATA[microsoft]]></category>

		<category><![CDATA[webstandards]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/03/16/bring-down-ie-6.html</guid>
		<description>&lt;p&gt;&amp;#8220;&amp;#8230;it&amp;#8217;s finally time to take IE6 behind the shed and shoot it.&amp;#8221; &lt;/p&gt;
&lt;p&gt;-&lt;a href="http://stopdesign.com/archive/2009/03/16/bring-down-ie-6.html"&gt;archive link&lt;/a&gt;-&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>&#8220;&#8230;it&#8217;s finally time to take IE6 behind the shed and shoot it.&#8221; </p>
<p>-<a href="http://stopdesign.com/archive/2009/03/16/bring-down-ie-6.html">archive link</a>-</p><img src="http://feeds.feedburner.com/~r/stopdesign/~4/vlDybjsdN5I" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/03/16/bring-down-ie-6.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Fluid Grids</title>
		<link>http://alistapart.com/articles/fluidgrids</link>
		<comments>http://stopdesign.com/archive/2009/03/04/fluid-grids.html#comments</comments>
		<pubDate>Thu, 05 Mar 2009 04:28:33 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
		
		<category><![CDATA[links]]></category>

		<category><![CDATA[css]]></category>

		<category><![CDATA[grid]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/03/04/fluid-grids.html</guid>
		<description>&lt;p&gt;I love this in-depth look at implementing grids for liquid layouts. Ethan goes into detail just how it all fits together, and the magic formula needed to make it all work. Now if we could just have the ability to easily scale images inside a liquid layout (without resorting to clipping background images), we&amp;#8217;d be golden (pun intended). &lt;/p&gt;
&lt;p&gt;-&lt;a href="http://stopdesign.com/archive/2009/03/04/fluid-grids.html"&gt;archive link&lt;/a&gt;-&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>I love this in-depth look at implementing grids for liquid layouts. Ethan goes into detail just how it all fits together, and the magic formula needed to make it all work. Now if we could just have the ability to easily scale images inside a liquid layout (without resorting to clipping background images), we&#8217;d be golden (pun intended). </p>
<p>-<a href="http://stopdesign.com/archive/2009/03/04/fluid-grids.html">archive link</a>-</p><img src="http://feeds.feedburner.com/~r/stopdesign/~4/WW_TtM8atp8" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/03/04/fluid-grids.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>Wanted: Layout System</title>
		<link>http://meyerweb.com/eric/thoughts/2009/02/17/wanted-layout-system/</link>
		<comments>http://stopdesign.com/archive/2009/02/17/wanted-layout-system.html#comments</comments>
		<pubDate>Tue, 17 Feb 2009 19:00:00 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
		
		<category><![CDATA[links]]></category>

		<category><![CDATA[css]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/02/18/wanted-layout-system.html</guid>
		<description>&lt;p&gt;Eric Meyer elaborates on why we need a better layout mechanism for web content (whether it be via CSS or not). We know we shouldn&amp;#8217;t use tables for layout. Floats are a hack, positioning is flawed, and &lt;code&gt;display:table-cell&lt;/code&gt; is no better than using a table itself. But Eric explains here why table &lt;em&gt;behavior&lt;/em&gt; works moderately well for layout:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;&amp;#8230; this is why the old “only use tables for layout” argument keeps coming up over and over: strip away the overheated rhetoric and obvious link-baiting, and you find the core of a real need. Because as powerful as CSS can be, table cells do certain things very easily that CSS makes very, very hard. Cells stretch vertically, keeping equal heights as a matter of their intrinsic nature. They stay out of each others’ way, while still being allowed to sit next to each other and use any sizing dimensions. They tie their layout to their parent elements, and vice versa. &lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;-&lt;a href="http://stopdesign.com/archive/2009/02/17/wanted-layout-system.html"&gt;archive link&lt;/a&gt;-&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>Eric Meyer elaborates on why we need a better layout mechanism for web content (whether it be via CSS or not). We know we shouldn&#8217;t use tables for layout. Floats are a hack, positioning is flawed, and <code>display:table-cell</code> is no better than using a table itself. But Eric explains here why table <em>behavior</em> works moderately well for layout:</p>
<blockquote><p>&#8230; this is why the old “only use tables for layout” argument keeps coming up over and over: strip away the overheated rhetoric and obvious link-baiting, and you find the core of a real need. Because as powerful as CSS can be, table cells do certain things very easily that CSS makes very, very hard. Cells stretch vertically, keeping equal heights as a matter of their intrinsic nature. They stay out of each others’ way, while still being allowed to sit next to each other and use any sizing dimensions. They tie their layout to their parent elements, and vice versa. </p></blockquote>
<p>-<a href="http://stopdesign.com/archive/2009/02/17/wanted-layout-system.html">archive link</a>-</p><img src="http://feeds.feedburner.com/~r/stopdesign/~4/Gl_JiREfYGY" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/02/17/wanted-layout-system.html/feed</wfw:commentRss>
		</item>
		<item>
		<title>WordPress plugins in use</title>
		<link>http://stopdesign.com/archive/2009/02/16/wp-plugins.html</link>
		<comments>http://stopdesign.com/archive/2009/02/16/wp-plugins.html#comments</comments>
		<pubDate>Mon, 16 Feb 2009 16:17:54 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
		
		<category><![CDATA[entries]]></category>

		<category><![CDATA[software]]></category>

		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://stopdesign.com/?p=1182</guid>
		<description>&lt;p&gt;There are a few WordPress plugins that help me publish this site as I want it. Here are a few of the key plugins I currently use on Stopdesign.&lt;span id="more-1182"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;ul class="marked"&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href="http://wordpress.org/extend/plugins/amazon-showcase-wordpress-widget/"&gt;Amazon Showcase&lt;/a&gt;&lt;/strong&gt; by &lt;a href="http://aaronforgue.com/"&gt;Aaron Forgue&lt;/a&gt;&lt;br /&gt;
Drop in any ISBN and this plugin takes care of the rest for Amazon reading and recommendation lists.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href="http://wordpress.org/extend/plugins/live-comment-preview/"&gt;Live Comment Preview&lt;/a&gt;&lt;/strong&gt; by &lt;a href="http://bradt.ca/"&gt;Brad Touesnard&lt;/a&gt;&lt;br /&gt;
Lots of plugins generate a real-time comment preview. This one seemed to be easy to configure and get working right away.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href="http://wordpress.org/extend/plugins/postalicious/"&gt;Postalicious&lt;/a&gt;&lt;/strong&gt; by &lt;a href="http://neop.gbtopia.com/"&gt;Pablo Gomez&lt;/a&gt;&lt;br /&gt;
This plugin automagically pulls in my Delicious links on an hourly basis, publishing an entry for each link I create. (It can also be configured to publish sets of links in a single entry too.) It&amp;#8217;s a useful plugin for automating posting of links created elsewhere &amp;#8212; it can also handle ma.gnolia, Google Reader, Reddit, or Yahoo Pipes. Pablo, the author, is incredibly responsive. After I emailed him a casual suggestion on a Saturday afternoon, he had a new version of the plugin (with my suggestion incorporated) in my Inbox later that same evening.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href="http://wordpress.org/extend/plugins/twitter-for-wordpress/"&gt;Twitter for WordPress&lt;/a&gt;&lt;/strong&gt; by &lt;a href="http://rick.jinlabs.com/"&gt;Ricardo González&lt;/a&gt;&lt;br /&gt;
Set it, and forget it.&amp;trade; Once installed and configured the way I wanted it, I&amp;#8217;ve never had to think about my tweets showing up on the site again.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href="http://wordpress.org/extend/plugins/wp-super-cache/"&gt;WP Super Cache&lt;/a&gt;&lt;/strong&gt; by &lt;a href="http://ocaoimh.ie/"&gt;Donncha O Caoimh&lt;/a&gt;&lt;br /&gt;
A must for speedy page-load times and to keep the server humming along, especially on high-traffic days.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href="http://wordpress.org/extend/plugins/search-unleashed/"&gt;Search Unleashed&lt;/a&gt;&lt;/strong&gt; by &lt;a href="http://urbangiraffe.com/"&gt;John Godley&lt;/a&gt;&lt;br /&gt;
Does several cool tricks with search for a WordPress site, including query term highlighting and searching across every post and comment field. I&amp;#8217;m using the plugin for the results page, itself. But I wasn&amp;#8217;t able to use the query term highlighting on entry pages because that conflicted with pages cached with WP Super Cache, and I wasn&amp;#8217;t able to figure out how to prevent caching of entry pages referred by a search.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A friendly reminder: some authors put in lots of time and effort into plugins that are free for us to use at will. If you can afford to, send a donation their way, especially for plugins that do any heavy lifting for your site.&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>There are a few WordPress plugins that help me publish this site as I want it. Here are a few of the key plugins I currently use on Stopdesign.<span id="more-1182"></span></p>
<ul class="marked">
<li><strong><a href="http://wordpress.org/extend/plugins/amazon-showcase-wordpress-widget/">Amazon Showcase</a></strong> by <a href="http://aaronforgue.com/">Aaron Forgue</a><br />
Drop in any ISBN and this plugin takes care of the rest for Amazon reading and recommendation lists.</li>
<li><strong><a href="http://wordpress.org/extend/plugins/live-comment-preview/">Live Comment Preview</a></strong> by <a href="http://bradt.ca/">Brad Touesnard</a><br />
Lots of plugins generate a real-time comment preview. This one seemed to be easy to configure and get working right away.</li>
<li><strong><a href="http://wordpress.org/extend/plugins/postalicious/">Postalicious</a></strong> by <a href="http://neop.gbtopia.com/">Pablo Gomez</a><br />
This plugin automagically pulls in my Delicious links on an hourly basis, publishing an entry for each link I create. (It can also be configured to publish sets of links in a single entry too.) It&#8217;s a useful plugin for automating posting of links created elsewhere &#8212; it can also handle ma.gnolia, Google Reader, Reddit, or Yahoo Pipes. Pablo, the author, is incredibly responsive. After I emailed him a casual suggestion on a Saturday afternoon, he had a new version of the plugin (with my suggestion incorporated) in my Inbox later that same evening.</li>
<li><strong><a href="http://wordpress.org/extend/plugins/twitter-for-wordpress/">Twitter for WordPress</a></strong> by <a href="http://rick.jinlabs.com/">Ricardo González</a><br />
Set it, and forget it.&trade; Once installed and configured the way I wanted it, I&#8217;ve never had to think about my tweets showing up on the site again.</li>
<li><strong><a href="http://wordpress.org/extend/plugins/wp-super-cache/">WP Super Cache</a></strong> by <a href="http://ocaoimh.ie/">Donncha O Caoimh</a><br />
A must for speedy page-load times and to keep the server humming along, especially on high-traffic days.</li>
<li><strong><a href="http://wordpress.org/extend/plugins/search-unleashed/">Search Unleashed</a></strong> by <a href="http://urbangiraffe.com/">John Godley</a><br />
Does several cool tricks with search for a WordPress site, including query term highlighting and searching across every post and comment field. I&#8217;m using the plugin for the results page, itself. But I wasn&#8217;t able to use the query term highlighting on entry pages because that conflicted with pages cached with WP Super Cache, and I wasn&#8217;t able to figure out how to prevent caching of entry pages referred by a search.</li>
</ul>
<p>A friendly reminder: some authors put in lots of time and effort into plugins that are free for us to use at will. If you can afford to, send a donation their way, especially for plugins that do any heavy lifting for your site.</p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/e5jECfJ5sww" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/02/16/wp-plugins.html/feed</wfw:commentRss>
		</item>
	</channel>
</rss><!-- Dynamic page generated in 0.332 seconds. --><!-- Cached page generated by WP-Super-Cache on 2009-07-17 02:03:37 --><!-- Compression = gzip -->
