<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
   <channel>
      <title>Authentic Boredom</title>
      <link>http://cameronmoll.com/</link>
      <description></description>
      <language>en</language>
      <copyright>Copyright 2009</copyright>
      <lastBuildDate>Wed, 01 Jul 2009 06:33:30 -0700</lastBuildDate>
      <generator>http://www.sixapart.com/movabletype/</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

            <item>
         <title>Recent job listings</title>
         <description><![CDATA[<p>A few weeks ago I received the following remarks from Jeff Lin, an Authentic Jobs customer and founder of <a href="http://bustoutsolutions.com/">Bust Out Solutions</a>:</p>

<blockquote>Just wanted to let you know that I posted a job probably two years ago for a designer, got several responses, and ultimately found one guy who I tried to hire. It didn't work out at the time, but we kept in touch, and I finally hired him a few months ago. It's worked out great, and we recently launched <a href="http://bestbuyideax.com/">Best Buy Idea X</a>. I'm happy with the design, and in part thanks to Authentic Jobs for helping me find great talent!</blockquote>

<p>
Employers continue to find talented web and creative professionals through <a href="http://authenticjobs.com/">Authentic Jobs</a>, which has been filling full-time and freelance positions throughout the globe since 2005. And we keep giving back, too, using 1% of our revenue to fund <a href="http://www.kiva.org/lender/authenticjobs">74 loans to entrepreneurs around the world</a> via Kiva.org. Thank you.</p>

<p>Some recent listings are highlighted below.</p>

<p class="no-indent">
<strong>Full-time (International)</strong></p>
<ul>
	<li><strong class="jl">Cambridge, UK (or New York)</strong> <a href="http://authenticjobs.com/jobs/3685/">Senior PHP Developer</a> <span class="at">at</span> <span class="employer">English360</span></li>
	<li><strong class="jl">London, UK</strong> <a href="http://authenticjobs.com/jobs/3671/">Senior Developer</a> <span class="at">at</span> <span class="employer">Addison Corporate Marketing Limited</span></li>
</ul>

<p class="no-indent">
<strong>Full-time (U.S.)</strong></p>
<ul>
	<li><strong class="jl">Montgomery, AL</strong> <a href="http://authenticjobs.com/jobs/3676/">User Interface Designer/Developer</a> <span class="at">at</span> <span class="employer">Southern Poverty Law Center</span></li>
	<li><strong class="jl">Campbell, CA</strong> <a href="http://authenticjobs.com/jobs/3701/">Rockstar Designer</a> <span class="at">at</span> <span class="employer">ZURB, inc,</span></li>
	<li><strong class="jl">Cupertino, CA</strong> <a href="http://authenticjobs.com/jobs/3694/">Sr. Web Front-End Engineer</a> <span class="at">at</span> <span class="employer">Apple Inc.</span></li>
	<li><strong class="jl">Palo Alto, CA</strong> <a class="newpost" href="http://authenticjobs.com/jobs/3714/">Facebook Communication Designer</a> <span class="at">at</span> <span class="employer">Facebook</span></li>
	<li><strong class="jl">Santa Monica, CA</strong> <a class="newpost" href="http://authenticjobs.com/jobs/3710/">User Interface Engineer</a> <span class="at">at</span> <span class="employer">Demand Media</span></li>
	<li><strong class="jl">Boulder, CO</strong> <a href="http://authenticjobs.com/jobs/3696/">Junior Web Developer</a> <span class="at">at</span> <span class="employer">Wall Street On Demand</span></li>
	<li><strong class="jl">Washington, DC</strong> <a href="http://authenticjobs.com/jobs/3692/">Infographics Designer</a> <span class="at">at</span> <span class="employer">Pew Research Center</span></li>
	<li><strong class="jl">Washington, DC</strong> <a href="http://authenticjobs.com/jobs/3679/">Front-End Developer</a> <span class="at">at</span> <span class="employer">U.S. News &amp; World Report</span></li>
	<li><strong class="jl">Laurel, MD</strong> <a href="http://authenticjobs.com/jobs/3693/">Web Developer</a> <span class="at">at</span> <span class="employer">LMD</span></li>
	<li><strong class="jl">New York, NY</strong> <a href="http://authenticjobs.com/jobs/3675/">Web and E-Media Developer</a> <span class="at">at</span> <span class="employer">NYC Department of Transportation</span></li>
	<li><strong class="jl">Cleveland, OH</strong> <a href="http://authenticjobs.com/jobs/3665/">Contract Front-End Developer</a> <span class="at">at</span> <span class="employer">The Sherwin-Williams Company</span></li>
	<li><strong class="jl">Arlington, VA</strong> <a href="http://authenticjobs.com/jobs/3707/">Front-end Web Designer</a> <span class="at">at</span> <span class="employer">Symplicity Corporation</span></li>
	<li><strong class="jl">Seattle, WA</strong> <a href="http://authenticjobs.com/jobs/3677/">UI Developer</a> <span class="at">at</span> <span class="employer">Angry Lapdog Productions, Inc.</span></li>
	<li><strong class="jl">Seattle, WA</strong> <a class="newpost" href="http://authenticjobs.com/jobs/3715/">Web Developer</a> <span class="at">at</span> <span class="employer">msnbc.com</span></li>
</ul>

<p class="no-indent">
<strong>Freelance</strong></p>
<ul>
	<li><a class="newpost" href="http://authenticjobs.com/jobs/3716/">Freelance Sr. Web Developer</a> <span class="at">at</span> <span class="employer">Magnani Caruso Dutton</span></li>
	<li><a class="newpost" href="http://authenticjobs.com/jobs/3712/">Web Application UI/UX Designer</a> <span class="at">at</span> <span class="employer">Fantastic</span></li>
	<li><a href="http://authenticjobs.com/jobs/3687/">Mozilla Firefox Extension Developer</a> <span class="at">at</span> <span class="employer">SEOmoz</span></li>
</ul>

<p>
Post a job or find one at <a href="http://authenticjobs.com/">Authentic Jobs</a>.</p>]]></description>
         <link>http://cameronmoll.com/archives/2009/07/recent_job_listings_9/</link>
         <guid>http://cameronmoll.com/archives/2009/07/recent_job_listings_9/</guid>
        
        
         <pubDate>Wed, 01 Jul 2009 06:33:30 -0700</pubDate>
      </item>
            <item>
         <title>The debate over page zooming vs. text scaling</title>
         <description><![CDATA[<p>
After posting <a href="http://cameronmoll.com/archives/2009/06/coding_like_its_1999/">my reasons for switching back to <code>px</code> for <code>font-size</code></a> citing page zooming as the primary justification, it was apparent that enthusiasm for page zooming wasn't as unanimous as I had thought.</p>

<p>
As a refresher from the article, low-vision users (or anyone) can alter their browser's text size by changing the default text size permanently via the browser&#8217;s settings, or on-the-fly using the keyboard commands <code>Ctrl+</code>/<code>-</code> (Windows) or <code>Command+</code>/<code>-</code> (Mac).</p>
 
<p>
Until recently, these commands would cause all major browsers to scale up or down the size of the text while retaining the formatting and layout of the page, commonly called <strong>text scaling</strong> or <strong>text zooming</strong>.  Now, however, recent versions of every major browser now default to <strong>page zooming</strong> instead of text scaling for <code>Ctrl+</code>/<code>-</code> and <code>Command+</code>/<code>-</code> commands AND for the "Zoom" option in the browser's menu. Page zooming literally zooms the entire page &#8212; layout, formatting, and text size &#8212; in unison. Elements retain their size and shape, which greatly reduces the need for us to compensate for text scaling. In effect, the browser assumes the burden of relative sizing.</p>

<p>
Below are examples of each. First, <a href="http://screencast.com/t/BJZ2Qu99CO4">page zooming</a>:</p>

<div class="snap">
<object width="374" height="313"> <param name="movie" value="http://content.screencast.com/users/cameronmoll/folders/Jing/media/6e4b9e3f-569e-479e-acc3-9b5c6b67c771/jingswfplayer.swf"></param> <param name="quality" value="high"></param> <param name="bgcolor" value="#FFFFFF"></param> <param name="flashVars" value="thumb=http://content.screencast.com/users/cameronmoll/folders/Jing/media/6e4b9e3f-569e-479e-acc3-9b5c6b67c771/FirstFrame.jpg&amp;containerwidth=374&amp;containerheight=313&amp;loaderstyle=jing&amp;content=http://content.screencast.com/users/cameronmoll/folders/Jing/media/6e4b9e3f-569e-479e-acc3-9b5c6b67c771/00000006.swf"></param> <param name="allowFullScreen" value="true"></param> <param name="scale" value="showall"></param> <param name="allowScriptAccess" value="always"></param> <param name="base" value="http://content.screencast.com/users/cameronmoll/folders/Jing/media/6e4b9e3f-569e-479e-acc3-9b5c6b67c771/"></param>  <embed src="http://content.screencast.com/users/cameronmoll/folders/Jing/media/6e4b9e3f-569e-479e-acc3-9b5c6b67c771/jingswfplayer.swf" quality="high" bgcolor="#FFFFFF" width="374" height="313" type="application/x-shockwave-flash" allowScriptAccess="always" flashVars="thumb=http://content.screencast.com/users/cameronmoll/folders/Jing/media/6e4b9e3f-569e-479e-acc3-9b5c6b67c771/FirstFrame.jpg&amp;containerwidth=374&amp;containerheight=313&amp;loaderstyle=jing&amp;content=http://content.screencast.com/users/cameronmoll/folders/Jing/media/6e4b9e3f-569e-479e-acc3-9b5c6b67c771/00000006.swf" allowFullScreen="true" base="http://content.screencast.com/users/cameronmoll/folders/Jing/media/6e4b9e3f-569e-479e-acc3-9b5c6b67c771/" scale="showall"></embed> </object>
</div>

<p style="padding-top: 1em;">
Next, <a href="http://screencast.com/t/MRek8q8kpZr">text scaling</a>:</p>

<div class="snap">
<object width="374" height="321"> <param name="movie" value="http://content.screencast.com/users/cameronmoll/folders/Jing/media/e1f6efb3-d2e0-4362-9df6-ebff5a9ba143/jingswfplayer.swf"></param> <param name="quality" value="high"></param> <param name="bgcolor" value="#FFFFFF"></param> <param name="flashVars" value="thumb=http://content.screencast.com/users/cameronmoll/folders/Jing/media/e1f6efb3-d2e0-4362-9df6-ebff5a9ba143/FirstFrame.jpg&containerwidth=374&containerheight=321&loaderstyle=jing&content=http://content.screencast.com/users/cameronmoll/folders/Jing/media/e1f6efb3-d2e0-4362-9df6-ebff5a9ba143/00000007.swf"></param> <param name="allowFullScreen" value="true"></param> <param name="scale" value="showall"></param> <param name="allowScriptAccess" value="always"></param> <param name="base" value="http://content.screencast.com/users/cameronmoll/folders/Jing/media/e1f6efb3-d2e0-4362-9df6-ebff5a9ba143/"></param>  <embed src="http://content.screencast.com/users/cameronmoll/folders/Jing/media/e1f6efb3-d2e0-4362-9df6-ebff5a9ba143/jingswfplayer.swf" quality="high" bgcolor="#FFFFFF" width="374" height="321" type="application/x-shockwave-flash" allowScriptAccess="always" flashVars="thumb=http://content.screencast.com/users/cameronmoll/folders/Jing/media/e1f6efb3-d2e0-4362-9df6-ebff5a9ba143/FirstFrame.jpg&containerwidth=374&containerheight=321&loaderstyle=jing&content=http://content.screencast.com/users/cameronmoll/folders/Jing/media/e1f6efb3-d2e0-4362-9df6-ebff5a9ba143/00000007.swf" allowFullScreen="true" base="http://content.screencast.com/users/cameronmoll/folders/Jing/media/e1f6efb3-d2e0-4362-9df6-ebff5a9ba143/" scale="showall"></embed> </object>
</div>

<p>
If you're running Firefox or Safari on Mac or Windows, you can easily switch between these two options. Select the "Zoom Text Only" option under the "View" or "Zoom" menus to override page zooming.</p>

<h3 class="article-sub">So, what's wrong with page zooming?</h3>

<p>
There are at least two compelling arguments I've heard that are unfavorable towards page zooming, and I am listening to what is being said:</p>

<p>
<strong>"Low-vision users don't like horizontal scrolling."</strong> I've not done extensive research in this area myself, so it's hard to counter-argue. Besides, it's safe to say nobody -- good vision or not -- likes horizontal scrolling.</p>

<p>
However, I'd like to see conclusive evidence that accompanies statements such as this from "Nik", who <a href="/archives/2009/06/coding_like_its_1999/index.html#046296">commented</a> in my previous article:</p>

<blockquote>We found during usability testing for a site with a large proportion of users with vision problems that most of them preferred to use text zoom instead of page zoom because page zoom almost always means horizontal scrolling.</blockquote>

<p>
We need to know more about how these users configure their browsers in the first place, the keyboard commands they do and don't use, and the like. Being asked to rate the two options in a usability lab vs. configuring and using one's own computer are often two very different things.</p>

<p>
<strong>"What about IE6?"</strong> First, if your project, organization, or client still requires supporting IE6, you have far worse things to be concerned about than page zooming vs. text scaling. I have the luxury of not being concerned about IE6 in my corporate and personal projects. That is not a luxury afforded to everyone.</p>

<p>
With IE6, only text scaling is an option. IE6 (and 7 and 8 actually) will not rescale <code>px</code> values. There are valid arguments for and against this approach, but regardless the only option for text scaling in IE6 is with <code>em</code> and <code>%</code> values. So, if supporting IE6 is still part of your game plan, the argument here is that relative values should be too.</p>

<h3 class="article-sub">Is one site for all feasible?*</h3>

<p>
For me, at the core of this debate is a much bigger question: <strong>Is one site for all really feasible?</strong> Traditionally, I've believed it is. But increasingly I'm finding that it's not always practical. Some examples:</p>
<ul>
	<li>I make the argument in <a href="http://www.mobilewebbook.com/"><em>Mobile Web Design</em></a> that a mobile-optimized site is better for mobile users than a handheld style sheet that marginally modifies your existing site. I published this book nearly two years ago, and today I still believe that to be true, as do several other mobile experts.</li>
	<li>Although I argue repeatedly in "<a href="http://cameronmoll.com/articles/extensible-css/">The Highly Extensible CSS Interface</a>" in favor or markup that endures the rigors of language translation, there are often elements (menus, buttons, etc.) within an interface that are virtually impossible or impractical to code in way such that any amount of text can be fitted properly. I'm seeing this right now with a project at work that has to be translated in 10 languages. The more practical solution has been to have a style sheet for each language, <code>(language).css</code>, that modifies the width, height, padding, etc. of those elements that cannot be compensated for otherwise.</li>
	<li>In his article for A List Apart, "<a href="http://www.alistapart.com/articles/lowvision/">Big, Stark &amp; Chunky</a>", Joe Clark points out the fact that merely compensating for text scaling may not be enough for low-vision users. Separate CSS files specifically for these users may be needed. "Standardistas were able to stomach the idea that blind people were simply ignoring the appearance of their sites because, self-evidently, they were blind," he states. "It was no big deal; nothing happens to your visual design when you accommodate blind people. But to accommodate low-vision people, you have to totally rearrange your multicolumn site. You have to knowingly destroy your original graphic design."</li>
</ul>

<p>
The reality of all this debate is the fact that, as I've already mentioned, every major browser seems to be trending towards page zooming as the default for the "Zoom" option, whether via keyboard or menu option. This trend, along with the other arguments in this article, leaves me unsettled about the right approach for extensibility within a layout, and even unsettled about <code>px</code> for <code>font-size</code>.</p>

<p>
So, if you were expecting a conclusion of some sort at the end of this article, there isn't one. I'm thinking aloud. Please do the same -- let's keep the discussion going.</p>

<p>
<strong>Additional reading:</strong></p>
<ul>
	<li><a href="http://allinthehead.com/retro/343/the-fallacy-of-page-zooming">Drew McLellan: The Fallacy of Page Zooming</a></li>
	<li><a href="http://zomigi.com/blog/why-browser-zoom-shouldnt-kill-flexible-layouts/">Zoe Mickley Gillenwater: Why Browser Zoom Shouldn't Kill Flexible Layouts</a></li>
	<li><a href="http://www.betalogue.com/2009/06/15/safari-4-zoom/">Pierre Igot: Safari 4's Full-Page Zoom: Impressive</a></li>
	<li><a href="http://www.otal.umd.edu/uupractice/vision/">Universal Usability in Practice: Blind and Low Vision User</a></li>
</ul>

<p>
<em>* This heading text is taken from a report of the same name, "Helping low-vision and other users with Web sites that meet their needs: is one site for all feasible?" by Mary Frances Theofanos and Janice Redish. The report, which is one of the references in Joe Clark's article, <a href="http://www.rotarytraderonline.com/shop/asinsearch_B00096ZKBY.htm">can be purchased here</a>.</em></p>]]></description>
         <link>http://cameronmoll.com/archives/2009/06/page_zooming_vs_text_scaling/</link>
         <guid>http://cameronmoll.com/archives/2009/06/page_zooming_vs_text_scaling/</guid>
        
        
         <pubDate>Thu, 18 Jun 2009 08:45:19 -0700</pubDate>
      </item>
            <item>
         <title>Coding like it&apos;s 1999</title>
         <description><![CDATA[<p><strong class="s2">UPDATE:</strong> Please see <a href="http://cameronmoll.com/archives/2009/06/page_zooming_vs_text_scaling/">The debate over page zooming vs. text scaling</a>.</p>

<p>
Recently I made the switch back to HTML 4 for <code>DOCTYPE</code>s and <code>px</code> for <code>font-size</code> (sound like 1999 again?), and I've <a href="http://twitter.com/cameronmoll/status/1883497041">tweeted</a> about it occasionally. I'm documenting the switch more thoroughly here.
</p>

<h3 class="article-sub">HTML 4.01 Strict</h3>

<p>
I've chosen to go with HTML 4.01 Strict as the <code>DOCTYPE</code> in my projects moving forward, favoring it above XHTML 1.0 Strict and HTML 5. I'll briefly explain my reasoning.
</p>

<p>
<strong>XHTML 1.0 Strict</strong> &ndash; This is what many of us in the industry, including myself, have been using for the past few years. However, Dave Shea offers <a href="http://mezzoblue.com/archives/2009/04/20/switched/">a compelling argument to drop XHTML</a> with an eye towards HTML 5:
</p>

<blockquote>"Six years ago, many of us thought XHTML would be the future of the web and we'd be living in an XML world by now. But in the intervening time it's become fairly apparent to myself and others that XHTML2 really isn't going anywhere, at least not in the realm that we care about....  I'm not ready to start working through the contortions needed to make my sites work with an HTML5 DOCTYPE yet, which leaves me with the most recent implemented version of the language.... [U]ntil I get a better sense that HTML5 has arrived, 4.01 will do me just fine for the next four or five years."</blockquote>

<p>
<strong>HTML 5</strong> &ndash; In a nutshell, HTML 5 is the next major version of the hypertext markup language. The good news is meaningless <code>div</code> and <code>span</code> elements will be replaced by more meaningful elements such as <code>nav</code>, <code>header</code>, and <code>video</code>. 
</p>

<p>
This means instead of marking up something such as
</p>

<pre style="margin: 5px 0;"><code>&lt;div class="header"&gt;
  &lt;h1&gt;Page Title&lt;/h1&gt;
&lt;/div&gt;</code></pre>

<p>
or 
</p>

<pre style="margin: 5px 0;"><code>&lt;object&gt;&lt;param&gt;&lt;embed src="<a href="http://vimeo.com/3956190">http://vimeo.com/3956190</a>"&gt;&lt;/embed&gt;&lt;/param&gt;&lt;/object&gt;</code></pre>

<p>
we'll be able to mark up the same HTML like this:
</p>

<pre style="margin: 5px 0;"><code>&lt;header&gt;
  &lt;h1&gt;Page Title&lt;/h1&gt;
&lt;/header&gt;</code></pre>

<p>
and this:
</p>

<pre style="margin: 5px 0;"><code>&lt;video src="<a href="http://vimeo.com/3956190">http://vimeo.com/3956190</a>"&gt;</code></pre>

<p>
The bad news is HTML 5 is not currently supported adequately by major browsers (notably Internet Explorer). Estimates range from months to years before HTML 5 is fully supported and therefore a viable option for all of us creating websites.
</p>

<p>
An alternate approach is to maintain that same watchful eye towards HTML 5 by writing markup using current <code>DOCTYPE</code>s but with semantic, HTML 5-like <code>class</code> names. Jon Tan covers this approach beautifully in "<a href="http://jontangerine.com/log/2008/03/preparing-for-html5-with-semantic-class-names">Preparing for HTML5 with Semantic Class Names</a>".
</p>

<p>
For example, using the <code>nav</code> element, HTML 5 markup would be
</p>

<pre style="margin: 5px 0;"><code>&lt;nav&gt;
  &lt;ul&gt;
    &lt;li&gt;&lt;a href=""&gt;Item 1&lt;/a&gt;&lt;/li&gt;
    ...
  &lt;/ul&gt;
&lt;/nav&gt;</code></pre>

<p>
while our semantic, HTML 5-like markup using HTML 4 or XHTML 1 would be
</p>

<pre style="margin: 5px 0;"><code>&lt;div class="nav"&gt;
  &lt;ul&gt;
    &lt;li&gt;&lt;a href=""&gt;Item 1&lt;/a&gt;&lt;/li&gt;
    ...
  &lt;/ul&gt;
&lt;/div&gt;</code></pre>

<p>
However, the drawback to this approach is you potentially end up with a lot of extra <code>div</code>s. If our goal is meaningful and lightweight markup, the most optimal markup <em>right now</em> would instead be the following:
</p>

<pre style="margin: 5px 0;"><code>&lt;ul class="nav"&gt;
  &lt;li&gt;&lt;a href=""&gt;Item 1&lt;/a&gt;&lt;/li&gt;
  ...
&lt;/ul&gt;</code></pre>

<p>
So, my opinion about HTML 5? <strong>We'll all adapt just fine when it's ready for prime-time and fully supported.</strong> The mental shift will be minimal. Until then, I'll keep coding the way we've always done it.
</p>

<p>
Additional resources:
</p>

<ul>
	<li><a href="http://cameronmoll.com/archives/2009/01/12_resources_for_html5/">12 resources for getting a jump on HTML 5</a></li>
	<li><a href="http://en.wikipedia.org/wiki/HTML_5">Wikipedia: HTML 5</a></li>
	<li><a href="http://adactio.com/journal/1540">Adactio: The Rise of HTML 5</a></li>
	<li><a href="http://radar.oreilly.com/2009/05/google-bets-big-on-html-5.html">O'Reilly: Google Bets Big on HTML 5</a></li>
	<li><a href="http://www.webmonkey.com/blog/Google_Throws_Its_Weight_Behind_HTML_5">Webmonkey: Google Throws Its Weight Behind HTML 5</a></li>
</ul>

<h3 class="article-sub" style="padding-top: 15px;">px for font-size</h3>

<p>
For a number of years, <code>px</code> was the de facto standard for sizing text with <code>font-size</code>. It gave designers transferring their design from Photoshop (or other software) to HTML a consistent, absolute unit for text size. Then, as we became more knowledgeable of and concerned with accessibility, relative text size (<code>em</code> or <code>%</code>) gradually became the preferred unit. This enabled low-vision users, and really anybody, to change their browser's default text size permanently via the browser's settings, or on-the-fly using the keyboard commands <code>Ctrl+</code> and <code>Ctrl-</code> (Windows) or <code>Command+</code> and <code>Command-</code> (Mac).
</p>
 
<p>
Accordingly, and up until recently, all major browsers would scale up or down the size of the text  while retaining the formatting and layout of the page. This is commonly called <strong>text scaling</strong> or <strong>text zooming</strong>. This adaptation required us to create markup that allowed for relative sizing of any elements containing text. For example, if a <code>div</code> contained text set atop a background image, we would have to either repeat the image as the <code>div</code> grew larger with text scaling or create the image larger than necessary to compensate for growth. This is something I covered in detail in my "<a href="http://cameronmoll.com/archives/2008/02/the_highly_extensible_css_interface_the_series/">The Highly Extensible CSS Interface</a>" series of articles.
</p>

<p>
However, recent versions of every major browser -- Safari, Firefox, Google Chrome, Opera, and yes, Internet Explorer -- now default to <strong>page zooming</strong> instead of text scaling for <code>Ctrl+</code>/<code>-</code> and <code>Command+</code>/<code>-</code> commands. Page zooming literally zooms the entire page -- layout, formatting, and text size -- in unison. Elements retain their size and shape, which greatly reduces the need to compensate for text scaling. In effect, the browser assumes the burden of relative sizing.
</p>

<p>
What does all this mean? <strong>It means <code>px</code> can again be considered a viable value for <code>font-size</code>.</strong> It means the difference between setting text with absolute units or setting text with relative units is negligible for users. For you and me, however, the the difference is substantial. The burden of calculating relative units throughout a CSS document is replaced by the convenience of absolute units -- <code>14px</code> is <code>14px</code> anywhere in the document, independent of parent elements whose <code>font-size</code> may differ.
</p>

<p>
Additional resources:
</p>

<ul>
<li><a href="http://www.wilsonminer.com/posts/2007/mar/16/problem-pixels/">Wilson Miner: The problem with pixels</a></li>
	<li><a href="http://www.456bereastreet.com/archive/200703/ie_7_does_not_resize_text_sized_in_pixels/">456 Berea Street: IE 7 does not resize text sized in pixels</a></li>
	<li><a href="http://mezzoblue.com/archives/2008/10/07/zoom/">Mezzoblue: Zoom</a></li>
	<li><a href="http://orderedlist.com/articles/hello-old-friend">Ordered List: Hello Old Friend</a></li>
</ul>

<p>I suppose the only legacy practice left to switch back to at this point is tables...</p>

<p><strong class="s2">UPDATE:</strong> Some of you may have been led to believe I've given a mandate for the industry to move to HTML 4 and px. Please note I've documented only my switch here and the reasoning for it, and that px <em>can be considered a viable value</em> for font-size. As I mention in the comments, you need to make the right decision based on <em>your</em> audience and users. If XHTML and relative sizing is the right choice for your project, no one else can tell you otherwise.</p>]]></description>
         <link>http://cameronmoll.com/archives/2009/06/coding_like_its_1999/</link>
         <guid>http://cameronmoll.com/archives/2009/06/coding_like_its_1999/</guid>
        
        
         <pubDate>Thu, 04 Jun 2009 08:39:04 -0700</pubDate>
      </item>
            <item>
         <title>Free download: Good vs. Great Design (summary)</title>
         <description><![CDATA[<div class="snap"><a href="/speaking/misc/good-vs-great.pdf" style="border-bottom: 0;"><img class="picC" src="/img/pics/goodgreat-pdf.gif" alt="First page of Good vs. Great PDF" width="367" height="475" /></a></div>

<p>If you've not yet signed up for next month's <a href="http://howconference.com/">HOW Design Conference</a> in Austin, Texas, now is the time to do so.</p>

<p>The conference organizers have been gracious enough to allow me to publicly post the handout that will be provided in my session, "Good vs. Great Design". This 10-page summary of my presentation is something I've been hoping to compile for quite some time now, and HOW has finally provided the impetus for making it happen.</p>

<div class="download">
<img class="vdiv" src="/img/download.gif" alt="" width="14" height="14" /> <a href="/speaking/misc/good-vs-great.pdf">Download good-vs-great.pdf (PDF, 588 KB)</a>
</div>

<p>Highlights from other sessions and speakers include:</p>

<ul>
<li>Print to Web Breakthrough</li>
<li>The Secret of Project Management for In-House Designers</li>
<li>Keeping Creative Control with Difficult Clients</li>
<li>Communicating Up, Down and All Around the Organization</li>
<li>10 Things You Didn&#8217;t Know Fonts Could Do</li>
<li>Craft + Activism = Craftivism</li>
<li>Studio tours (frog design, Olive Interactive Design &amp; Marketing, others) for pre-conference attendees</li>
<li>DJ Stout (Pentagram), Thomas Phinney (Adobe), Cynthia Rapp (Cartoon Network), Lia Braaten Hager (Proctor &amp; Gamble), and nearly 50 other speakers</li>
</ul>

<p>Hope to see you there.</p>]]></description>
         <link>http://cameronmoll.com/archives/2009/05/free_download_good_vs_great_design/</link>
         <guid>http://cameronmoll.com/archives/2009/05/free_download_good_vs_great_design/</guid>
        
        
         <pubDate>Tue, 19 May 2009 08:09:54 -0700</pubDate>
      </item>
            <item>
         <title>Authentic Jobs: Advice for Staying Gainfully Employed</title>
         <description><![CDATA[<p>The <a href="http://cameronmoll.com/archives/2009/01/design_review_critique_me/">redesign</a> for <a href="http://authenticjobs.com/">Authentic Jobs</a>, which is coming along swimmingly thanks to your feedback, will include a blog to allow myself and others to post articles on the topic of employment, freelancing, and the like.</p>

<p>The following is one such article. I've been bookmarking the links below over the past few months in anticipation of the new blog. However, because the redesign is taking longer than I had hoped, I've decided to post the article now given the timeliness of the subject.</p>

<p>The last 6 months or so have been rocky for just about everyone and every business, and with layoffs and budget cutbacks, job search is certainly no exception. Many more applicants, but far fewer job openings. The good news is that things seem to be on the way up. We saw the same number of freelance listings in April as we did in January, but full-time listings increased by 34%. Currently on the site, you'll find listings from <a href="http://authenticjobs.com/jobs/3482/">Apple</a>, <a href="http://authenticjobs.com/jobs/3537/">HUGE</a>, <a href="http://authenticjobs.com/jobs/3518/">Facebook</a>, <a href="http://authenticjobs.com/jobs/3493/">frog design inc.</a>, <a href="http://authenticjobs.com/jobs/3497">Berklee College of Music</a>, <a href="http://authenticjobs.com/jobs/3525/">Backcountry.com</a>, <a href="http://authenticjobs.com/jobs/3510/">Comcast</a>, <a href="http://authenticjobs.com/jobs/3559/">Magnani Caruso Dutton</a>, and plenty of other great companies small and large.</p>

<p>On to the advice. Whether you're on the clock with an employer or a full-time freelancer, I'm fairly certain you'll find the following remarks from authors around the globe to be helpful for staying gainfully employed in today's economy.</p>

<p class="no-indent"><strong>Ross Johnson:</strong> <a href="http://www.3point7designs.com/blog/2009/02/22/how-to-respond-to-an-authentic-jobs-posting/">How to Respond to an Authentic Jobs Posting</a></p>

<p>Ross Johnson of 3.7 Designs posted a freelance listing on Authentic Jobs, then in turn offered advice to those replying to his and other listings. He offers 6 tips for applying, one of which is the following:</p>

<blockquote>I was surprised at how many applications failed to answer questions I specifically asked to have included. Others ignored large portions of the listing (like experience with common open source CMS solutions). Even if you had no experience (or little) I spent twice as long considering the applicants who at least addressed all of the points.</blockquote>

<p class="no-indent"><strong>smashLAB:</strong> <a href="http://www.ideasonideas.com/2009/04/stop-acting-like-a-sissy-and-market-your-company/">Stop acting like a sissy and market your company</a></p>

<p>Eric Karjaluoto of smashLAB argues in favor of maintaining or even increasing marketing efforts during tough times, not decreasing them. "The problem-of-the-day has less to do with numbers," Eric mentions, and more to do with "fear, panic and our own knee-jerk reactions."</p>

<blockquote>What baffles me about all of this is how people are choosing to cut their spending. I can appreciate reducing office space or negotiating a lower lease rate. I similarly understand reducing staff members or entertaining job sharing options. What I can’t quite grasp, however, is this tendency to narrow the pipe for incoming sales. When you aren’t getting dates, you don’t go home and watch re-runs of Matlock; you get out of the house and meet people.</blockquote>

<blockquote>A nice office space doesn’t directly drive sales. Office perks may heighten morale but they don’t necessarily bring in new clients. In times like these, all of us have to look at what keeps the machine running. As such, there’s one simple truth that I want you to embrace: your company has to accelerate its marketing and sales efforts.</blockquote>

<p class="no-indent"><strong>Design Observer:</strong> <a href="http://www.designobserver.com/archives/entry.html?id=38880">Designing Through the Recession</a></p>

<p>A top-notch article by none other than top-notch advice giver Michael Bierut. </p>

<blockquote>In your desperation to compete for work, you'll be tempted to do things that you might not do when times are good: take on work for a shady client, start a project without a contract, ship a finished job to someone who's fallen behind on an agreed payment schedule. Do not do these things. Not only will they not help, they will almost certainly end in tears, probably your own.</blockquote> 

<blockquote>The modern design studio can't help but subscribe to the cult of asap. But while working at full speed is great for profit margins, it's not so good for quality control. A design solution almost always benefits from a second, third or fourth look. Take advantage of the slower pace of a recession by remembering what it was like in design school to spend a full semester on a single project. What seemed then like torture may now feel like a luxury, and your work will benefit.</blockquote>

<p class="no-indent"><strong>New York Times Opinion:</strong> <a href="http://arieff.blogs.nytimes.com/2009/04/08/designing-through-a-depression/">Designing Through a Depression</a></p>

<p>Partly a response to The Times' own article arguing design loves depression (which received a <a href="http://www.designobserver.com/archives/entry.html?id=38886">well-deserved rebuttal</a> from Design Observer), Allison Arieff's piece encourages using the power of design to make smarter choices for the consumer and the environment.</p>

<blockquote>Maybe one way the recession as good for design is to see it not as a form of punishment for frivolous designers but rather as an opportunity to allow for a rethinking of design itself — and the role of the designer within it. This rethinking needs to come not just from designers but from the manufacturers, companies and other clients who decide what products and projects will be produced. There’s no excuse not to examine and re-examine what’s made, how it’s manufactured, what materials are used (and which are recyclable), what benefit it’s giving the consumer (or lack thereof) and what contribution, if any, it’s making to anything other than landfill.</blockquote>

<p class="no-indent"><strong>D. Keith Robinson:</strong> <a href="http://happymasochist.com/posts/view/hanging_in_and_helping/">Hanging In and Helping</a></p>

<p>Keith, co-founder of Blue Flavor, on staying ethical in difficult times:</p>

<blockquote>If you’re running your business scared and making all your decisions by fear I think you’re doing it wrong, regardless of the economic situation. I know I didn’t start a business just to survive and get by. This <strong>will</strong> pass. It might take awhile, but it will and I want to be right with my business and myself when it does. I’d rather go down fighting for what’s right than bend a bunch of rules just to get by.</blockquote>

<p class="no-indent"><strong>A List Apart:</strong> <a href="http://www.alistapart.com/articles/fillingyourdancecard">Filling Your Dance Card in Hard Economic Times</a></p>

<p>A solid round-up of advice by Pepi Ronalds for freelancers and full-timers alike.</p>

<blockquote>People in our industry enjoy far more flexibility than ever before, due to the buoyant economy we’ve had for the last decade. The new economy won’t eliminate flexible working arrangements, but employers and clients do have more bargaining power and may expect more of you. Your employers won’t necessarily ask you to work longer, but they will ask you to be more focused, committed, accountable, and reliable when you’re in the office. They’ll appreciate it when you arrive on time and that you work when you’re at work. Minimize chats and distractions. Shut down personal messaging programs, Facebook, email, etc., until you’re on break or until the end of the day.</blockquote>

<p class="no-indent"><strong>Boagworld:</strong> <a href="http://boagworld.com/business-strategy/5-options-when-website-budgets-get-slashed">5 options when website budgets get slashed</a></p>

<p>Paul Boag:</p>

<blockquote>We spend the majority of our ever decreasing budgets on adding bells and whistles to existing websites when there are large number of potential customers who never reach our sites. Instead of sinking your budget and efforts solely into your website consider looking further afield. Could your web strategy be better served by putting resources into a Facebook group or a twitter account for example? ... Ask yourself where your target audience congregates. Instead of constantly trying to draw users to your site begin to spend time where they already meet.</blockquote>

<p class="no-indent"><strong>New York Times:</strong> <a href="http://www.nytimes.com/2009/03/14/technology/start-ups/14startup.html?_r=2&ref=smallbusiness">Weary of Looking for Work, Some Create Their Own</a></p>

<p>A report from the New York Times on several entrepreneurs around the United States making the most of a largely barren job market. </p>

<blockquote>Economists say there are some peculiarities to this wave of downturn start-ups. Chiefly, the Internet has given people an extraordinary tool not just to market their ideas but also to find business partners and suppliers, and to do all kinds of functions on the cheap: keeping the books, interacting with customers, even turning a small idea into a big idea.
</blockquote>

<blockquote>The goal for many entrepreneurs nowadays is not to create a company that will someday make billions but to come up with an idea that will produce revenue quickly, said Jerome S. Engel, director for the center for entrepreneurship at the Berkeley Haas School of Business. Mr. Engel said many people will focus on serving immediate needs for individuals and businesses.</blockquote>

<p class="no-indent"><strong>Think Vitamin:</strong> <a href="http://thinkvitamin.com/business/15-tips-for-freelancers-starting-their-own-business/">15 Tips for Freelancers Starting Their Own Business</a></p>

<p>A generally helpful list of tips from Ed Raynham, particularly this one:</p>

<blockquote>You should contact the customer on a regular basis (every 3 months if the job is over) to inquire how things are going. This will help to make the customer feel important and that you are still interested in their business even though the project is finished. It will also help to keep you in their mind for future projects. Try to avoid a sales push with every contact else this goodwill will be broken and they will dread your calls.</blockquote>

<p class="no-indent"><strong>Jeffrey Zeldman:</strong> <a href="http://24ways.org/2008/recession-tips-for-web-designers">Recession Tips For Web Designers</a></p>

<blockquote>Running a traditional business is like securing a political position in Chicago: it costs a fortune. That’s why bad times crush so many companies. But you are a creature of the internets. You don’t need an office to do great work. I ran Happy Cog out of my apartment for far longer than anyone realized. My clients, when they learned my secret, didn’t care.</blockquote>

<blockquote>Web design is a people business. If things are slow, email former clients. If you just lost your job, email former agency clients with whom you worked closely to inform them of your freelance business and find out how they’re doing. Best practice: focus the email on wishing them a happy holiday and asking how they’re doing. Let your email signature file tell them you’re now the president of Your Name Design. Leading with the fact that you just lost your job may earn sympathy (or commiseration: the client may have lost her job, too) but it’s not exactly a sure-fire project getter.</blockquote>

<p class="no-indent"><strong>Shimon Rura:</strong> <a href="http://geeksinboston.com/2009/01/26/working-from-home-why-it-sucks/">Working from Home: Why It Sucks</a></p>

<p>The reason I've included this article? It highlights the imperative need for in-person feedback. I take for granted how helpful this is in full-time employment. And if I ever go back to freelancing, this observation has changed my perception (positively) towards flying in to meet with <em>every</em> client at the start and throughout the project.</p>

<blockquote>In an office you get feedback constantly. At the coffee pot in the morning, eye contact shows interest in your latest tasks, or nods express sympathy about difficult colleagues and bosses. When you have a question about something, your coworker’s eyes and facial expressions will tell you, consciously or subconsciously, if you’re sounding smart or stupid. Chances are, you depend on this feedback more than you realize. You need it both for work-specific communication, which is easy to see, and for maintaining your self-image, esteem, and motivation–which is harder to see because the mechanisms are subconscious.</blockquote>

<p>There you have it. Take some time to peruse the articles I've linked to. Add a comment for other articles that should have been included here. </p>]]></description>
         <link>http://cameronmoll.com/archives/2009/05/authentic_jobs_employment_advice/</link>
         <guid>http://cameronmoll.com/archives/2009/05/authentic_jobs_employment_advice/</guid>
        
        
         <pubDate>Thu, 07 May 2009 06:52:51 -0700</pubDate>
      </item>
            <item>
         <title>Poster officially on sale, and Kindle+Kiva giveaway</title>
         <description><![CDATA[<div class="snap"><a href="http://cameronmoll.bigcartel.com/product/letterpress-poster-16x24" style="border-bottom: 0;"><img class="picC" src="/img/pics/poster-stack.jpg" alt="Stack of freshly printed letterpress posters" width="367" height="489" /></a></div>

<p>
Yesterday I finally retrieved a very large stack of letterpress posters, freshly printed and ready for shipping. More than half of the 350 available to the public in this press run have already been pre-ordered. Order yours here:</p>

<ul>
<li><a href="http://cameronmoll.bigcartel.com/product/letterpress-poster-16x24">$75 unsigned</a></il>
<li><a href="http://cameronmoll.bigcartel.com/product/signed-letterpress-poster-16x24">$100 signed</a></il>
</ul>

<p>
Also, <strong>the first 50 customers to order beginning today</strong> will be entered to win a <a href="http://www.amazon.com/gp/product/B00154JDAI?ie=UTF8&amp;tag=authenticbore-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=B00154JDAI">Kindle 2</a> and $75 gift certificate for <a href="http://www.kiva.org/">Kiva</a>, which can be used to lend microloans to entrepreneurs in developing countries. One gift for you, and potentially many gifts for them. (The Kiva funds are perpetual -- as entrepreneurs repay their loans to you, you can reloan and reloan again.)</p>

<div class="snap"><img class="picC" src="/img/pics/kindlekiva.png" alt="Amazon Kindle 2 and Kiva" width="367" height="165" /></div>

<p>
Total combined value: <strong>US $434</strong>. One winner will be randomly selected once 50 orders have been placed.</p>

<p>Posters will begin shipping immediately. $10 shipping to anywhere in the United States. $20 to Canada. $35 to any of these countries: Australia, Austria, Denmark, Finland, France, Germany, Greece, Ireland, Italy, Japan, The Netherlands, New Zealand, Norway, Poland, Singapore, Slovakia, South Africa, Sweden, Switzerland, Turkey, United Arab Emirates, United Kingdom. If your country is not listed, please <a href="http://cameronmoll.bigcartel.com/contact">contact me</a> to add it to the list.</p>

<p>If shipping within Utah, use code UTAH at checkout to receive discounted shipping (5% off your order).</p>

<p>Additional detail photos available at <a href="http://ideas.veer.com/portfolio/1395">my Veer portfolio</a>.</p>

<div class="update">
<h3>The Fine Print</h3>
No purchase necessary. To enter without purchase, send a postcard to PO Box 1525, Salt Lake City, Utah, United States. Entries must be received by May 31, 2009. Many will enter, one will win picked by random number. Void where prohibited. 
</div>]]></description>
         <link>http://cameronmoll.com/archives/2009/04/poster_on_sale_kindle_kiva_giveaway/</link>
         <guid>http://cameronmoll.com/archives/2009/04/poster_on_sale_kindle_kiva_giveaway/</guid>
        
        
         <pubDate>Fri, 24 Apr 2009 06:28:26 -0700</pubDate>
      </item>
            <item>
         <title>Is it time to move beyond 960?</title>
         <description><![CDATA[<div class="snap"><a href="http://typographica.org/" style="border-bottom: 0;"><img class="picC" src="/img/pics/typographica.jpg" alt="The new Typographica.org" width="367" height="247" /></a></div>
<p style="text-indent: 0; padding-top: 0; font-style: italic; font-size: 11px; color: #888;">The new <a href="http://typographica.org/">Typographica.org</a>, which uses a width of 1040.</p>

<p><strong>Lately I've been questioning if it isn't time to move beyond 960 for websites, and if so, what the ideal width may be.</strong></p>

<p>Those of you frequenting this site for a few years may recall a similar quandary, "<a href="http://www.cameronmoll.com/archives/001220.html">Optimal width for 1024px resolution?</a>". In it, I proposed 960 as the ideal width for moving beyond 800x600:</p>

<blockquote>I’ve been using 960 for some time now, as it’s slightly smaller than full width, and it’s divisible by 3, 4, 5, 6, 8, 10, 12, 15, and 16 (imagine the grid possibilities).</blockquote>

<p>Since then it seems 960 has nearly become the de facto standard for fixed-width designs on the web. A number of Photoshop, browser, and OS plug-ins default to it. There's even an entire <a href="http://960.gs/">CSS framework built on 960</a>. (I should note 984 has also seen considerable usage, most notably Apple.com.)</p>

<p>Admittedly, I've not yet settled on an ideal width for 1280ish, and I'm working on only one site at the moment to inform my thinking about the topic. But I think we're at the point where it's time to talk amongst ourselves.</p>

<p><strong>Before the flak begins flying from fixed-width naysayers,</strong> I remind you that I'm a huge fan of fluid designs with <code>min-width</code> and <code>max-width</code> limits, as evidenced by my <a href="http://cameronmoll.com/articles/extensible-css/">Extensible CSS series</a> and <a href="http://cameronmoll.com/projects/book/">case study design</a> for <a href="http://www.amazon.com/gp/product/1590596145?ie=UTF8&amp;tag=authenticbore-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=1590596145"><em>CSS Mastery</em></a>. But I believe there will always be a need for fixed width, and frankly in many ways it's more practical than fluid width.</p>

<p><strong>So what's the ideal width?</strong> I'm not sure yet. Let's figure it out together. Here's what I've got so far:</p>

<ul>
<li><strong>1020</strong> is divisible by 2, 3, 4, 5, 6, 10, 12, 15 but not 8 and 16. It's not much wider than 960.</li>
<li><strong>1040</strong> is divisible by 2, 4, 5, 8, 10, 16 but not 3, 12, or 15. Yet it has a reasonable width that sits somewhere between the lower end of 960 and higher end of users browsing full screen (many don't, of course).</li>
<li><strong>1080</strong>, which is what I'm <a href="http://twitter.com/cameronmoll/status/1581656589">taking for a spin</a> with a site right now, is divisible 2, 3, 4, 5, 6, 8, 10, 12, 15 but not 16. It pushes the upper end of the width spectrum, and measure (line length) could become an issue if not dealt with appropriately.</li>
</ul>

<p>Of course, there's probably a slew of other numbers between 960 and 1080 divisible by many of the widths listed above, so speak your mind about widths, measure, pros, cons, etc.</p>]]></description>
         <link>http://cameronmoll.com/archives/2009/04/is_it_time_to_move_beyond_960/</link>
         <guid>http://cameronmoll.com/archives/2009/04/is_it_time_to_move_beyond_960/</guid>
        
        
         <pubDate>Thu, 23 Apr 2009 09:35:17 -0700</pubDate>
      </item>
            <item>
         <title>Design Considerations for Touch UI</title>
         <description><![CDATA[<div style="margin-bottom: 8px;">
<object width="367" height="275"><param name="allowfullscreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="movie" value="http://vimeo.com/moogaloop.swf?clip_id=4206140&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=0&amp;show_portrait=1&amp;color=00adef&amp;fullscreen=1" /><embed src="http://vimeo.com/moogaloop.swf?clip_id=4206140&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=0&amp;show_portrait=1&amp;color=00adef&amp;fullscreen=1" type="application/x-shockwave-flash" allowfullscreen="true" allowscriptaccess="always" width="367" height="275"></embed></object>
</div>

<p>Gestural (touch) UI is gaining momentum as a suitable companion, and in some cases worthy replacement, to the traditional UI via peripheral device input.</p>

<p>Of course, with this momentum comes revised thinking about how we design for interaction. To this end, San Francisco-based <a href="http://www.punchcut.com/">Punchcut</a>, an agency specializing in mobile design, threw together a very brief <a href="http://www.vimeo.com/4206140">video</a> demonstrating five considerations to keep in mind when designing for touch. (Beautiful job on motion design btw, guys.)</p>

<p>The more detailed article that preceded the video can be found here: <a href="http://idlemode.com/2009/04/10/design-considerations-for-touch-ui/">Design Considerations for Touch UI</a>.</p>]]></description>
         <link>http://cameronmoll.com/archives/2009/04/design_considerations_for_touch_ui/</link>
         <guid>http://cameronmoll.com/archives/2009/04/design_considerations_for_touch_ui/</guid>
        
        
         <pubDate>Tue, 21 Apr 2009 08:16:46 -0700</pubDate>
      </item>
            <item>
         <title>Drummer Tony Williams: &quot;Good Musicians Copy&quot;</title>
         <description><![CDATA[<div class="snap"><a href="http://www.morrisonhotelgallery.com/photographer/default.aspx?photographerID=32" style="border-bottom: 0;"><img class="picC" src="/img/pics/tonywilliams.jpg" alt="Tony Williams" width="367" height="367" /></a></div>
<p style="text-indent: 0; padding-top: 0; font-style: italic; font-size: 11px; color: #888;">Tony Williams, NYC 1965. Photograph by <a href="http://www.morrisonhotelgallery.com/photographer/default.aspx?photographerID=32">Francis Wolff</a>.</p>

<p>
<a href="http://en.wikipedia.org/wiki/Tony_Williams">Tony Williams</a>, arguably one of the most influential and revolutionary drummers of the 20th century, clearly understood a concept that I tried to demystify, and probably fell short of demystifying, nearly 6 years ago. Published in June 2003, "Good Designers Copy, Great Designers Steal" was an attempt to describe the idea of becoming a better designer by dissecting, analyzing, and "copying" the works of other designers. (Sorry, you'll have to Google that article -- it's painful to link up at this point given its age...)</p>

<p>
It was during our recent flight to Rome that I stumbled on the following, nestled toward the end of a very thorough article by John Ephland for <em>Traps</em> magazine (Spring 2009 issue). The text is formed from an interview with Tony Williams in October 1988. Check out how Tony explains it:</p>

<blockquote>
If you're going to pick just one style of playing and you can only play that way, that's what you want to do ... I don't discourage that. But I think that <strong>drumming</strong> is more important than <strong>style</strong>. When I've given lessons or clinics, I try to emphasize that learning how to play the drums is more important than having your own style. Really knowing what the drums can do and the scope and range of the instrument is more important.
</blockquote>

<p>
He continues, explaining how he "set about religiously" to play other drummers' style in an attempt to understand the scope and range of his instrument:
</p>

<blockquote>
You know the reason I play the way I do is because, when I first started playing, all I ever wanted to do was to sound like Max Roach, was to sound like Art Blakey, was to sound like Philly Joe Jones, was to sound like Louis Hayes, was to sound like Jimmy Cobb, was to sound like Roy Haynes. I really wanted to figure out why they sounded the way they did. I wasn't interested in my own style. So I set about playing like these guys religiously, and playing their style because it was just such a wonderful, magical experience. It was just a marvelous, wonderful feeling that I got when I heard these people and then I developed a way to sound like them, and to go about it. I mean, it was exciting to me to figure out how he did that.
</blockquote>

<p>
Tony beat me to it by 15 years, but that's precisely the point I was hoping to make in my original article -- you become a good designer by familiarizing yourself with the methods and techniques used by those who are already good designers. Such is the advice Tony would give to emerging drummers:</p>

<blockquote>
I get guys coming up to me -- they just got a drum set; they've been playing maybe four years -- and they want their own style. They want to be expressive. I say, 'Well, then, if you want to be expressive, you've got to find out what the instrument will do. And to do that, you've got to go back and find out and get an idea of what's already been done.'
</blockquote>

<p>
And to cap it all off, Tony's remarks conclude with this appropriate summary:</p>

<blockquote>
That's what the instrument's all about. It's the instrument that's more important. The quality and magic of the instrument are more important than you are.
</blockquote>

<p>
That's what design is all about. It's the instrument of design that's more important. The quality and magic of what design can do are more important than you are.
</p>

<p>
Tony Williams died in 1997. I owe him a posthumous thank you for saying something far better than I could.</p>]]></description>
         <link>http://cameronmoll.com/archives/2009/04/drummer_tony_williams_good_musicians_copy/</link>
         <guid>http://cameronmoll.com/archives/2009/04/drummer_tony_williams_good_musicians_copy/</guid>
        
        
         <pubDate>Thu, 09 Apr 2009 08:57:46 -0700</pubDate>
      </item>
            <item>
         <title>Letterpress poster: Pre-ordering now available</title>
         <description><![CDATA[<div class="snap"><a href="http://cameronmoll.bigcartel.com/product/letterpress-poster-16x24" style="border-bottom: 0;"><img class="picC" src="/img/pics/bigcartel-poster.jpg" alt="Letterpress poster product page" width="367" height="387" /></a></div>

<p>Several of you asked for the option to pre-order one of my letterpress posters currently being reprinted. Over the weekend this option was provided to those on the notification list. The general public is now welcome to pre-order. (As of this writing, just over 100 of the 350 prints that will be available have been pre-ordered.)</p>

<ul>
<li><a href="http://cameronmoll.bigcartel.com/product/letterpress-poster-16x24">$75 unsigned</a></il>
<li><a href="http://cameronmoll.bigcartel.com/product/signed-letterpress-poster-16x24">$100 signed</a></il>
</ul>

<p>Posters are being printed on the same paper and press (<a href="http://www.bjornpress.com/">Bjørn Letterpress Studio</a>), and your order will ship <strong>sometime in April 2009</strong>.</p>

<p>$10 shipping to anywhere in the United States. $20 to Canada. $35 to any of these countries: Australia, Austria, Denmark, Finland, France, Germany, Greece, Ireland, Italy, Japan, The Netherlands, New Zealand, Norway, Poland, Singapore, Slovakia, South Africa, Sweden, Switzerland, Turkey, United Arab Emirates, United Kingdom. If your country is not listed, please <a href="http://cameronmoll.bigcartel.com/contact">contact me</a> to add it to the list.</p>

<p>If shipping within Utah, use code UTAH at checkout to receive discounted shipping (5% off your order).</p>

<p>Additional detail photos available at <a href="http://ideas.veer.com/portfolio/1395">my Veer portfolio</a>.</p>]]></description>
         <link>http://cameronmoll.com/archives/2009/04/letterpress_poster_pre-order/</link>
         <guid>http://cameronmoll.com/archives/2009/04/letterpress_poster_pre-order/</guid>
        
        
         <pubDate>Mon, 06 Apr 2009 08:33:31 -0700</pubDate>
      </item>
            <item>
         <title>Roman Holiday</title>
         <description><![CDATA[<div style="margin-bottom: 8px;">
	<object width="377" height="217"><param name="allowfullscreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="movie" value="http://vimeo.com/moogaloop.swf?clip_id=3956190&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=1&amp;color=00adef&amp;fullscreen=1" /><embed src="http://vimeo.com/moogaloop.swf?clip_id=3956190&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=1&amp;color=00adef&amp;fullscreen=1" type="application/x-shockwave-flash" allowfullscreen="true" allowscriptaccess="always" width="377" height="217"></embed></object>
</div>

<p>
At the hotel and during the combined 15-hour flight home, a couple hours of video from a Canon HG10 and a little Final Cut Express led to the creation of <a href="http://vimeo.com/3956190">Roma Italia</a>, a brief video synopsis of our 5-day stay in Rome.</p>

<p>
Hope you enjoy it.</p>]]></description>
         <link>http://cameronmoll.com/archives/2009/04/roman_holiday/</link>
         <guid>http://cameronmoll.com/archives/2009/04/roman_holiday/</guid>
        
        
         <pubDate>Wed, 01 Apr 2009 10:11:41 -0700</pubDate>
      </item>
            <item>
         <title><![CDATA[Exploring Cuf&oacute;n, a sIFR alternative for font embedding]]></title>
         <description><![CDATA[<p>
Thanks to a <a href="http://twitter.com/jasonsantamaria/status/1242771147">tweet from Jason Santa Maria</a> a few weeks ago (and his help since), I was pointed to <a href="http://wiki.github.com/sorccu/cufon/about">Cuf&oacute;n</a>, which "aims to become a worthy alternative to sIFR, which despite its merits still remains painfully tricky to set up and use."</p>

<p>
I'll refer to these tests again in a minute, but feel free to jump ahead to these <a href="http://cameronmoll.com/articles/cufon/">Cuf&oacute;n test pages</a> that I've put together.
</p>

<p>
<a href="http://www.mikeindustries.com/blog/sifr/">sIFR</a>, as many of you are aware, is a means of replacing "short passages of plain browser text with text rendered in your typeface of choice, regardless of whether or not your users have that font installed on their systems" using a combination of Flash and JavaScript. <a href="http://www.shauninman.com/">Shaun Inman</a>, <a href="http://novemberborn.net/">Mark Wubben</a>, <a href="http://www.mikeindustries.com/">Mike Davidson</a>, and several others put in many long hours developing and refining IFR and sIFR, and we all owe them our gratitude for moving forward in a big way the state of typography on the web. These efforts continue today, as evidenced by this <a href="http://sxswtypography.com/">Web Typography mini-site</a> from a SXSW 2009 panel.</p>

<p>For many of us, however, the Flash part of these technologies makes it difficult to set up and use. (I personally have not opened Flash on my computer in literally 4 years, and I hope to keep that run alive.) Cuf&oacute;n, on the other hand, can be set up and run on your site in about 5 minutes. However, there are drawbacks compared to sIFR, which I'll get to towards the end of this article.</p>

<p>
What we really need to be working towards as an industry is <code><a href="http://www.css3.info/preview/web-fonts-with-font-face/">@font-face</a></code>. However, despite good browser support, <code>@font-face</code> faces EULA (end-user licensing agreement) issues similar to Cuf&oacute;n and seems much more difficult to configure than Cuf&oacute;n because of the proprietary Microsoft <code>.eot</code> files required to make it work. For additional information on <code>@font-face</code>, see Jon Tan's <a href="http://jontangerine.com/log/2008/10/font-face-in-ie-making-web-fonts-work">Making Web Fonts Work</a> and the aforementioned SXSW 2009 panel links.</p>

<p>Therefore, I personally see Cuf&oacute;n as an good interim step between sIFR and <code>@font-face</code>. Let's move on with getting it set up to use.</p>

<h3 class="article-sub">Setting Up Cuf&oacute;n</h3>

<p>Here's how Cuf&oacute;n works:</p>

<p>
<strong>Step 1:</strong> Download the Cuf&oacute;n script <a href="http://cufon.shoqolate.com/js/cufon-yui.js">compressed</a> or <a href="http://github.com/sorccu/cufon/tree/master/js/cufon.js">uncompressed</a>.</p>

<p>
<strong>Step 2:</strong> Upload the typeface of your choice using the <a href="http://cufon.shoqolate.com/generate/">Cuf&oacute;n generator</a>, which will provide you with a second script.</p>

<p>
<strong>Step 3:</strong> In the <code>&lt;head&gt;</code> of your document, add the Cuf&oacute;n script and the typeface script provided by the generator, such as:</p>
<pre style="margin: 0;"><code>&lt;script src="/scripts/cufon-yui.js" type="text/javascript"&gt;&lt;/script&gt;
&lt;script src="/scripts/KievitPro-Regular_400.font.js" type="text/javascript"&gt;&lt;/script&gt;</code></pre>

<p>
Also add this just before the closing <code>&lt;/body&gt;</code> tag to avoid a flicker issue in IE:</p>

<pre style="margin: 0 0 10px;"><code>&lt;script type="text/javascript">Cufon.now();&lt;/script&gt;</code></pre>

<p>
<strong>Step 4:</strong> Also in the <code>&lt;head&gt;</code>, indicate which HTML elements or selectors should be replaced with your typeface, such as:</p>
<pre style="margin: 0;"><code>&lt;script type="text/javascript"&gt;
  Cufon.replace('h1');
&lt;/script&gt;</code></pre>

<p>
or</p>

<pre style="margin: 0;"><code>&lt;script type="text/javascript"&gt;
  Cufon.replace('h1')('h2')('blockquote');
&lt;/script&gt;</code></pre>

<p>
Alternately, if you're using a JavaScript framework such as jQuery on the site where Cuf&oacute;n will be used, Cuf&oacute;n will take advantage of that framework's selector engine such that you can call out specific selectors like this: <code>Cufon.replace('#nav a')</code>.</p>

<p>
Or, if you're not using a framework, you'd reference these selectors using traditional (i.e. longer) JavaScript:</p>

<pre style="margin: 0 0 10px;"><code>Cufon.DOM.ready(function() {
  Cufon.replace(document.getElementById('nav').getElementsByTagName('a'));
});</code></pre>

<p>
<strong>Step 5:</strong> In your CSS file(s), modify any text replaced by Cuf&oacute;n the same way you would any other text -- <code>color: #333;</code> or <code>font-size: .87em;</code> or <code>text-transform: uppercase;</code> and so forth.</p>

<p>
<strong>And that's it.</strong> It really is as simple as that. Cufon is currently supported by IE 6/7/8, Firefox 1.5+, Safari 3+, Opera 9.5+, and Google Chrome. (See the <a href="http://wiki.github.com/sorccu/cufon">documentation on GitHub</a> for additional help, usage, and troubleshooting.)</p>

<h3 class="article-sub">Cuf&oacute;n Test Pages</h3>

<p>
Returning to the <a href="http://cameronmoll.com/articles/cufon/">Cuf&oacute;n test pages</a> I mentioned earlier, thumb through some of the samples to see FF Kievit Pro, Bickham Script Pro, Calgary Script, and Garamond Premier Pro rendered using Cuf&oacute;n.</p>

<div class="snap"><a href="http://cameronmoll.com/articles/cufon/bickham.html" style="border-bottom: 0;"><img class="picC" src="/img/pics/cufon-bickham.png" alt="Testing Bickham Script Pro with Cufon" width="367" height="250" /></a></div>

<div class="snap"><a href="http://cameronmoll.com/articles/cufon/calgary.html" style="border-bottom: 0;"><img class="picC" src="/img/pics/cufon-calgary.png" alt="Testing Calgary Script with Cufon" width="367" height="250" /></a></div>

<p>
Additionally, Cuf&oacute;n allows you to specify the units per em for which your typeface is rendered. a A lower value (e.g. 64 units per em) results in slightly better performance and smaller file size, but at the cost of rendering accuracy. On the <a href="http://cameronmoll.com/articles/cufon/quality">unit quality test page</a>, notice how poor the letterforms look at 64 units per em, compared to 256 or higher:</p>

<div class="snap"><a href="http://cameronmoll.com/articles/cufon/quality" style="border-bottom: 0;"><img class="picC" src="/img/pics/cufon-units.png" alt="Testing unit quality with Cufon" width="367" height="250" /></a></div>

<h3 class="article-sub">Drawbacks Compared to sIFR</h3>

<p>
It's worth pointing out Cuf&oacute;n is an emerging technology, though it is quickly evolving and improving. Because of this, there are several known issues or deficiencies, which include the following:</p>

<ul>
	<li><strong>No text selection.</strong> This is a big one. Currently you can't select the text to do something simple such as copy and paste.</li>
	<li><strong><del>No <code>a:hover</code> state.</del></strong> Update: <a href="http://groups.google.com/group/cufon/browse_thread/thread/0aff61c685171b92"><code>:hover</code> is now supported</a>.</li>
	<li><strong>Older PostScript fonts on Mac OS X aren't supported.</strong> This is a weird one, honestly. However, you can convert these files into a compatible format using <a href="http://wiki.github.com/sorccu/cufon/trouble-with-font-files">these instructions</a>.</li>
	<li><strong>Letterform fidelity may be inferior to sIFR.</strong> Adjusting the units per em may overcome this. So far in my tests, letterform fidelity has been sufficient for what I need.</li>
	<li><strong>Typeface information (files) may be easier to thieve than with sIFR.</strong> See next section.</li>
	<li><strong>Other <a href="http://wiki.github.com/sorccu/cufon/known-bugs-and-issues">known issues</a> I've not listed here.</strong></li>
</ul>

<h3 class="article-sub">EULA Licensing and Security</h3>

<p>
As of this writing, I'm in talks with type foundry <a href="http://www.fontfont.com/">FontFont</a>, type vendor <a href="http://veer.com/">Veer</a>, and Cuf&oacute;n creator <strong>Simo Kinnunen</strong> working through EULA (end-user licensing agreement) and security issues related to Cuf&oacute;n. There is a need to better understand what may be required by Cuf&oacute;n and its users to comply with type foundries' licensing -- or what alterations type foundries may be willing to make to their licensing -- to allow for font embedding technologies such as this.</p>

<p>
The main concern from the perspective of the type foundry appears to be that the typeface script generated by Cuf&oacute;n could be used to reverse engineer the very typeface itself. Further, because this script is a simple JavaScript file, it's readily available to anyone for copying and downloading. The counter argument here is that the script generated by Cuf&oacute;n results in a proprietary format that no current software can make use of, except Cuf&oacute;n itself.</p>

<p>The good news? Our talks have been very positive thus far. Technologies such as this encourage the use of typefaces other than the standard set we're all used to (Arial, Georgia, etc.) inevitably could increase the demand for typefaces. Therefore, type vendors and foundries have a vested interest in seeing <code>@font-face</code>, Cuf&oacute;n, and similar technologies flourish. Additionally, Simo Kinnunen is ready and willing to make adjustments to Cuf&oacute;n as needed.</p>

<h3 class="article-sub">Optimism on the Horizon</h3>

<p>
All things considered, I'm <em>extremely</em> optimistic about Cuf&oacute;n. I'm hopeful we'll be able to work through licensing and security issues such that all of us can use it freely in our projects. I've already got plans for it in a project I'm currently designing using FF Kievit Pro, only a coded snippet of which I can show for now:</p>

<div class="snap"><img class="picC" src="/img/pics/cufon-youth.png" alt="Testing Cufon with an actual project" width="367" height="190" /></div>

<p>
This site is expected to be translated into at least 10 languages, so you can imagine why Cuf&oacute;n could be a big advantage over traditional image replacement.</p>

<p>
So, <a href="http://cufon.shoqolate.com/generate/">give Cuf&oacute;n a try</a> and <a href="http://groups.google.com/group/cufon/">join in the discussion</a>. You just might end up a sIFR defector, too.</p>

<p>
<em>Special thanks again to Simo Kinnunen and Jason Santa Maria for bringing me up to speed with Cuf&oacute;n.</em></p>]]></description>
         <link>http://cameronmoll.com/archives/2009/03/cufon_font_embedding/</link>
         <guid>http://cameronmoll.com/archives/2009/03/cufon_font_embedding/</guid>
        
        
         <pubDate>Thu, 19 Mar 2009 10:00:43 -0700</pubDate>
      </item>
            <item>
         <title>The 5 P&apos;s of Twitter&apos;s runaway success</title>
         <description><![CDATA[<p><em>Hi there, respected Twitterer. Follow me at @<a href="http://twitter.com/cameronmoll">cameronmoll</a>.</em></p>

<p><a href="http://twitter.com/">Twitter</a>, the social ______ application for which no one can accurately describe its purpose (except <a href="http://www.vimeo.com/757146">this video</a>), became a runaway success last year. The San Francisco-based startup added 70% of its subscriber base in 2008 and is steadily growing in 2009, with an estimated 5,000 to 10,000 new accounts opened every day (<a href="http://www.marketingcharts.com/interactive/twitters-new-users-drive-600-growth-7324/">source</a>).</p>

<p>Actually, I think we enjoy <em>claiming</em> we can't describe what Twitter is, yet a closer inspection of it yields not only a better understanding of it but also why it's become <a href="http://www.thedailyshow.com/video/index.jhtml?videoId=219519&title=twitter-frenzy">so prevalent in the media</a> lately. And when that kind of inspection occurs, it's not surprising to the inspector why Twitter is where it's at today.</p>

<p><strong>1. Prudence.</strong> Twitter is solid proof that there is undeniable merit in doing just one thing -- as a business, as a strategy, as both -- and doing it really well. Users have 140 characters or less to share a thought, link up a URL, post a status update, or ask a question. That's it. Brilliant. </p>

<p>If Twitter lies at one end of the spectrum doing one thing really well, Facebook lies at the opposite end attempting to do all things well: status updates, networking, photos, videos, groups, etc. In terms of subscribers, Twitter's 6 million unique visitors lag far behind Facebook's 68 million (<a href="http://blog.compete.com/2009/02/09/facebook-myspace-twitter-social-network/">source</a>). These numbers clearly indicate many web users <em>currently</em> prefer the everything-but-the-kitchen-sink utility offered by Facebook, but I suspect Twitter has the potential to not only narrow the gap but even outlast its Palo Alto neighbor by merely doing one thing superbly well.</p>

<p>...until, of course, we're over Twitter too and we move on to the next technology. See #3.</p>

<p><strong>2. Pulse.</strong> I know of no more immediate way of gathering, monitoring, or responding to feedback about/for an idea, a question, a company, or an industry. Want to know what Twitter consumers are <a href="http://search.twitter.com/search?q=nike">saying about Nike</a> <em>right now?</em> How about <a href="http://search.twitter.com/search?q=lakers">the Lakers</a>? Or <a href="http://twitter.com/jkrums/status/1121915133">photos for breaking news</a> before any of the major media sources can report it? Or <a href="http://twitter.com/cameronmoll/status/795301823">which shoes to purchase</a>?</p>

<p>In fact, <a href="http://adage.com/digital/article?article_id=135016">AdAge reports</a> that Twitter is exploring even more ways of leveraging the Twitterverse for immediate feedback, enabling (from what I can gather) <a href="http://search.twitter.com/">search.twitter.com</a> to not only search previous tweets but also to generate new ones based on the search query. </p>

<p><strong>3. Proximity.</strong> It seems with every new web trend or technology we gradually draw closer in virtual proximity to persons we admire and to the authors of the content we consume. First, it was the personal or corporate website with its distant, one-way consumption of information. Then came blogs and the ability to generate two-way conversation with the author by commenting on content. And now we have Twitter, enabling one to engage in <a href="http://twitter.com/DaveJMatthews/status/1259674899">tweets with Dave Matthews</a> or to <a href="http://www.kottke.org/09/02/shaq-tweets">track down Shaq at a local diner</a>. </p>

<p><strong>4. Promotion.</strong> I've heard enough people complain there's no point to Twitter to come to this conclusion: You get back from Twitter what you put into it. Spend time and effort growing a network of followers, and soon enough you'll find Twitter to be a powerful promotion tool. For example, many of my initial letterpress poster sales back in December came as a result of my <a href="http://twitter.com/cameronmoll/status/1058908025">tweet</a>, not so much because of my <a href="http://cameronmoll.com/archives/2008/12/letterpress_poster_on_sale_today/">blog post</a>. Additionally, I use <a href="http://twitter.com/authenticjobs">automated tweets for Authentic Jobs</a> as another means of fostering business.</p>

<p>Follow a regimen akin to <a href="http://www.twitip.com/the-90-10-rule-for-successful-twitter-networking/">Jack Humphrey's 90-10 rule</a>, or whatever works for you, and you'll likely cultivate a valuable marketing resource.</p>

<p><strong>5. Prominence.</strong> I'm certain I'll get flak for this, but it's worth not beating around the bush to just come out and say it. Twitter puts one's <del>ego</del> follower count front and center. In the heyday of blogging, one could quickly estimate and deduce -- whether accurately or not, foolishly or prudently -- the prominence and traffic of a blog based on the average number of comments on articles or the <a href="http://www.feedburner.com/fb/a/home">FeedBurner</a> reader tally. These days it's <a href="http://twitterholic.com/">follower count</a>. It's unsurprising so many individuals and companies are sponsoring <a href="http://www.uncrate.com/men/uncrate/news/follow-us-on-twitter-win-stuff/">contests</a> to drive follower count upward, whether for intrinsic gratification or for promotional purposes. See #4. </p>

<p>Granted, certain individuals such as celebrities will garner large quantities of followers regardless of what they tweet about, but for many Twitterers, it remains a challenge to constantly be acquiring new followers.</p>

<p>So, when scrutinized as we've done here, Twitter really isn't such a mystery after all, is it?</p>]]></description>
         <link>http://cameronmoll.com/archives/2009/03/5_p_of_twitter/</link>
         <guid>http://cameronmoll.com/archives/2009/03/5_p_of_twitter/</guid>
        
        
         <pubDate>Thu, 05 Mar 2009 09:12:35 -0700</pubDate>
      </item>
            <item>
         <title>Recent job listings (and job search data)</title>
         <description><![CDATA[<p>
I was reviewing analytics data for Authentic Jobs this morning, and some figures emerged that are remarkable, but also somewhat unsurprising:</p>

<ul>
	<li>For the same monthly period one year ago, visits to the site have <strong>increased by 45.9%</strong> and average time on the site has <strong>increased by 22.9%</strong>.</li>
	<li>For the same annual period one year ago (technically two years ago), visits to the site have <strong>increased by 76.0%</strong> and average time on the site has <strong>decreased by 5.1%</strong>.</li>
</ul>

<p>
I say <em>somewhat unsurprising</em> because given the current economic climate, one can assume traffic to online job boards has increased in the last 6-12 months. Indeed, a recent report from comScore confirms this assumption: <a href="http://www.comscore.com/press/release.asp?press=2695">Job search ranked as the fastest growing U.S. online category in 2008</a>. Had comScore's study included other countries, the same trend would likely have emerged. 

<p>
Of course, Authentic Jobs welcomes any and all increases in traffic, and the site will continue to connect talented creative and web professionals with great work opportunities -- as it's been doing for nearly four years strong.</p>

<p>
Some recent listings are highlighted below.</p>

<p class="no-indent">
<strong>Full-time (U.S.)</strong></p>
<ul>
	<li><strong class="jl">Auburn, AL</strong> <a href="http://authenticjobs.com/jobs/3247/">Front-end Web Developer</a> <span class="at">at</span> <span class="employer">Politics4All</span></li>
	<li><strong class="jl">Cupertino, CA</strong> <a class="newpost" href="http://authenticjobs.com/jobs/3347/">Sr. Web UI Engineer</a> <span class="at">at</span> <span class="employer">Apple Inc.</span></li>
	<li><strong class="jl">Los Angeles, CA</strong> <a class="newpost" href="http://authenticjobs.com/jobs/3345/">Flash Developer</a> <span class="at">at</span> <span class="employer">HUGE</span></li>
	<li><strong class="jl">Palo Alto, CA</strong> <a href="http://authenticjobs.com/jobs/3269/">Product Designer</a> <span class="at">at</span> <span class="employer">Facebook</span></li>
	<li><strong class="jl">Golden, CO - Anywhere - Work Remotely</strong> <a class="newpost" href="http://authenticjobs.com/jobs/3346/">Gifted Web Developer</a> <span class="at">at</span> <span class="employer">RocketTheme, LLC</span></li>
	<li><strong class="jl">Washington, DC</strong> <a href="http://authenticjobs.com/jobs/3300/">Production Specialist (Web/Multimedia)</a> <span class="at">at</span> <span class="employer">AAAS</span></li>
	<li><strong class="jl">Lewes, Delaware</strong> <a href="http://authenticjobs.com/jobs/3260/">Senior Web Designer</a> <span class="at">at</span> <span class="employer">DecalGirl</span></li>
	<li><strong class="jl">West Springfield, MA</strong> <a href="http://authenticjobs.com/jobs/3332/">Web Marketing Manager</a> <span class="at">at</span> <span class="employer">Aspen Square Management</span></li>
	<li><strong class="jl">Lincoln, NE</strong> <a href="http://authenticjobs.com/jobs/3226/">Interactive Operations Manager</a> <span class="at">at</span> <span class="employer">Swanson Russell</span></li>	<li><strong class="jl">New York, NY</strong> <a href="http://authenticjobs.com/jobs/3239/">Web Designer</a> <span class="at">at</span> <span class="employer">Six Apart Inc.</span></li>
	<li><strong class="jl">Eugene, OR</strong> <a href="http://authenticjobs.com/jobs/3252/">Sr. Developer, Back-End</a> <span class="at">at</span> <span class="employer">GarageGames</span></li>
	<li><strong class="jl">Philadelphia</strong> <a href="http://authenticjobs.com/jobs/3230/">Web Designer</a> <span class="at">at</span> <span class="employer">Happy Cog Philadelphia</span></li>
	<li><strong class="jl">Alexandria, VA</strong> <a href="http://authenticjobs.com/jobs/3286/">Senior Frontend Web Developer</a> <span class="at">at</span> <span class="employer">MPRI</span></li>
</ul>

<p class="no-indent">
<strong>Freelance</strong></p>
<ul>
	<li><strong class="jl">Anywhere</strong> <a href="http://authenticjobs.com/jobs/3344/">Interaction designer</a> <span class="at">at</span> <span class="employer">Sideshow</span></li>
	<li><strong class="jl">Anywhere</strong> <a href="http://authenticjobs.com/jobs/3338/">Senior Designer Needed for Product Incubator</a> <span class="at">at</span> <span class="employer">Jason Reed Web Design</span></li>
	<li><strong class="jl">New York, NY</strong> <a href="http://authenticjobs.com/jobs/3336/">E-Commerce Web Designer</a> <span class="at">at</span> <span class="employer">Bonobos</span></li>
</ul>

<p>
Post a job or find one at <a href="http://authenticjobs.com/">Authentic Jobs</a>.
</p>]]></description>
         <link>http://cameronmoll.com/archives/2009/02/recent_job_listings_and_job_search_data/</link>
         <guid>http://cameronmoll.com/archives/2009/02/recent_job_listings_and_job_search_data/</guid>
        
        
         <pubDate>Wed, 25 Feb 2009 09:17:31 -0700</pubDate>
      </item>
            <item>
         <title>Speaking at HOW Design Conference in June</title>
         <description><![CDATA[<div class="snap"><a href="http://howconference.com/" style="border-bottom: 0;"><img class="picC" src="/img/pics/howconf.jpg" alt="Screen grab of HOW Conference website" width="367" height="273" /></a></div>

<p>I've been reading <a href="http://www.howdesign.com/">HOW magazine</a> on and off almost since I began my career as a designer 11 years ago. Every issue seems chock full of inspiring design, interviews with other designers I admire, and the like. Most issues land a permanent spot on my bookshelf.</p>

<p>For almost as long as I've associated myself with the magazine, I've had two wishes. These were never written down on paper. They existed only as an aspiration in the back of mind. The first was to have my work featured in a HOW design annual. The second was to speak at a HOW conference.</p>

<p>I have no idea the stars have aligned so perfectly in my favor, but this year I will fulfill both of those wishes. At the start of this year, one of my letterpress posters was <a href="http://flickr.com/photos/authentic/3153973545/in/set-72157610774240416/">recognized in the 2009 HOW In-House Design Annual</a>.</p>

<p>In June, I will be speaking at the <a href="http://howconference.com/">HOW Conference</a> in Austin, Texas for the first time. The event will run from June 24–27 and will be held in the same venue as SXSW, the Austin Convention Center.</p>

<p>Highlights include sessions and speakers such as:</p>

<ul>
<li>Print to Web Breakthrough</li>
<li>The Secret of Project Management for In-House Designers</li>
<li>Keeping Creative Control with Difficult Clients</li>
<li>Communicating Up, Down and All Around the Organization</li>
<li>10 Things You Didn't Know Fonts Could Do</li>
<li>Craft + Activism = Craftivism</li>
<li>Studio tours (frog design, Olive Interactive Design &amp; Marketing, others) for pre-conference attendees</li>
<li>DJ Stout (Pentagram), Thomas Phinney (Adobe), Cynthia Rapp (Cartoon Network), Lia Braaten Hager (Proctor &amp; Gamble), and nearly 50 other speakers</li>
</ul>

<p>I'm incredibly excited. <strong>Register by April 1 and save $100.</strong> Hope to see you there!</p>]]></description>
         <link>http://cameronmoll.com/archives/2009/02/speaking_at_how_conference/</link>
         <guid>http://cameronmoll.com/archives/2009/02/speaking_at_how_conference/</guid>
        
        
         <pubDate>Thu, 19 Feb 2009 08:51:50 -0700</pubDate>
      </item>
      
   </channel>
</rss>
