[Valid Atom 1.0] This is a valid Atom 1.0 feed.


This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.


  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <feed xmlns="">
  3.  <title>Josh Dick » Writing</title>
  4.  <subtitle>Thoughts on technology and more from Josh Dick.</subtitle>
  5.  <link rel="self" type="application/atom+xml" href="" />
  6.  <link rel="alternate" type="text/html" href="" />
  7.  <id></id>
  8.  <updated>2020-05-29T22:12:30-04:00</updated>
  9.  <author>
  10.    <name>Josh Dick</name>
  11.    <uri></uri>
  12.  </author>
  13.  <rights>© 2005-2020, Josh Dick</rights>
  14.  <entry>
  15.    <title>Tabclip: A Web Browser Extension</title>
  16.    <link rel="alternate" type="text/html" href="" />
  17.    <id>,2018:/2018/05/19/tabclip_a_web_browser_extension.html</id>
  18.    <published>2018-05-19T00:00:00-05:00</published>
  19.    <updated>2018-05-19T00:00:00-05:00</updated>
  20.    <author>
  21.      <name>Josh Dick</name>
  22.      <uri></uri>
  23.    </author>
  24.    <content type="html" xml:lang="en">
  25.        <![CDATA[<blockquote>Copy browser tabs to (and create browser tabs from) your clipboard.</blockquote><p>A few days ago, I released a new web browser extension for Mozilla Firefox and Google Chrome/Vivaldi called <a href="">tabclip</a> that allows you to copy browser tabs to (or create them from) your clipboard.</p>
  26. <p><img src="/post_assets/2018/05/tabclip_screenshot.png" alt="Tabclip Screenshot"></p>
  27. <p>The &ldquo;Copy&rdquo; button (and associated options) copy tab URLs to your clipboard.</p>
  28. <p>The &ldquo;Paste&rdquo; button attempts to find all URLs that appear in your clipboard, then opens each URL in a new browser tab.</p>
  29. <p>That&rsquo;s it!</p>
  30. <p>Tabclip is heavily inspired by Vincent Paré&rsquo;s <a href="">&ldquo;Copy All Urls&rdquo; Chrome extension</a>. I created tabclip because I wanted a similar extension that looked and worked the same in both Chrome and Firefox. Tabclip was written from scratch and shares no code with the &ldquo;Copy All Urls&rdquo; Chrome extension.</p>
  31. <p>You can get tabclip for Firefox <a href="">here</a> and for Chrome/Vivaldi <a href="">here</a>. Tabclip&rsquo;s source code is available at <a href="">its GitHub page</a>.</p>
  32. ]]>
  33.    </content>
  34.  </entry><entry>
  35.    <title>My Git Prompt for Zsh, Revisited</title>
  36.    <link rel="alternate" type="text/html" href="" />
  37.    <id>,2017:/2017/06/08/my_git_prompt_for_zsh_revisited.html</id>
  38.    <published>2017-06-08T00:00:00-05:00</published>
  39.    <updated>2017-06-08T00:00:00-05:00</updated>
  40.    <author>
  41.      <name>Josh Dick</name>
  42.      <uri></uri>
  43.    </author>
  44.    <content type="html" xml:lang="en">
  45.        <![CDATA[<blockquote>An elegant, bird&rsquo;s-eye view of your Git repositories.</blockquote><blockquote>
  46. <p><em>This post is a follow-up to my <a href="/2012/12/30/my_git_prompt_for_zsh.html">previous post</a> about the original version of my <code>zsh</code> Git prompt, which showed Git information on the right-hand side using <code>zsh</code>'s <code>RPS1</code> prompt.</em></p>
  47. <p><em><strong>Update on May 30, 2018:</strong> Updated the Git prompt code to be slightly cleaner.</em></p>
  48. </blockquote>
  49. <p>I like seeing useful information about <a href="">Git</a> repositories at a glance on the command line, and after using my <a href="/2012/12/30/my_git_prompt_for_zsh.html">previous Git prompt for <code>zsh</code></a> for about 4½ years, I decided it was time for some cosmetic tweaks and code cleanup.</p>
  50. <p>This prompt is functionally the same as the previous one, but has been moved from the right hand side to the left-hand side, and includes different symbols for showing the &ldquo;commits ahead/behind&rdquo; counts.</p>
  51. <p>Like the previous prompt, this prompt:</p>
  52. <ul>
  53. <li>Only appears if your current directory is a Git repository.</li>
  54. <li>Shows number of commits ahead and behind upstream, as applicable.</li>
  55. <li>Shows if a merge is currently taking place.</li>
  56. <li>Shows a &ldquo;traffic light&rdquo; representation of <code>git status</code>:
  57. <ul>
  58. <li>Red (<!-- raw HTML omitted -->●<!-- raw HTML omitted -->) means there are untracked changes.</li>
  59. <li>Yellow (<!-- raw HTML omitted -->●<!-- raw HTML omitted -->) means there are unstaged changes.</li>
  60. <li>Green (<!-- raw HTML omitted -->●<!-- raw HTML omitted -->) means there are staged changes.</li>
  61. </ul>
  62. </li>
  63. </ul>
  64. <p>Here&rsquo;s a contrived example that demonstrates how the prompt works (click on it for a larger version):</p>
  65. <p><!-- raw HTML omitted --><img src="/post_assets/2017/06/git_zsh_prompt.png" alt="Git Prompt for zsh"><!-- raw HTML omitted --></p>
  66. <p>While creating this updated version of my Git prompt, I looked into implementing it using <code>zsh</code>'s built-in <a href=""><code>vcs-info</code> mechanism</a>, but attempting to use it only made the code more complicated and cumbersome, so I decided against it.</p>
  67. <p>I use this prompt in combination with the excellent <a href=""><code>sickill/git-dude</code> Git commit notifier</a>, which automatically keeps repositories of your choosing up to date, and which will periodically trigger appropriate &ldquo;commits behind&rdquo; counts in the prompt when working with those repositories. This solution works great for my needs, but if you&rsquo;d prefer a <code>zsh</code> Git prompt that can keep repositories up to date on its own, check out <a href=""><code>sindresorhus/pure</code></a>.</p>
  68. <p>Here&rsquo;s the code for the prompt, as of this writing. (If I make any changes to the code in the future, the most up-to-date version will always be available <a href="">in my <code>.zshrc</code></a>.)</p>
  69. <p>You can paste this code directly into your <code>.zshrc</code>, or save it in its own file and source that file in your <code>.zshrc</code>.</p>
  70. <div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-zsh" data-lang="zsh">setopt prompt_subst
  71. autoload -U colors <span style="color:#f92672">&amp;&amp;</span> colors <span style="color:#75715e"># Enable colors in prompt</span>
  73. <span style="color:#75715e"># Echoes a username/host string when connected over SSH (empty otherwise)</span>
  74. ssh_info<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
  75.  <span style="color:#f92672">[[</span> <span style="color:#e6db74">&#34;</span>$SSH_CONNECTION<span style="color:#e6db74">&#34;</span> !<span style="color:#f92672">=</span> <span style="color:#e6db74">&#39;&#39;</span> <span style="color:#f92672">]]</span> <span style="color:#f92672">&amp;&amp;</span> echo <span style="color:#e6db74">&#39;%(!.%{$fg[red]%}.%{$fg[yellow]%})%n%{$reset_color%}@%{$fg[green]%}%m%{$reset_color%}:&#39;</span> <span style="color:#f92672">||</span> echo <span style="color:#e6db74">&#39;&#39;</span>
  76. <span style="color:#f92672">}</span>
  78. <span style="color:#75715e"># Echoes information about Git repository status when inside a Git repository</span>
  79. git_info<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
  81.  <span style="color:#75715e"># Exit if not inside a Git repository</span>
  82.  ! git rev-parse --is-inside-work-tree &gt; /dev/null 2&gt;&amp;<span style="color:#ae81ff">1</span> <span style="color:#f92672">&amp;&amp;</span> <span style="color:#66d9ef">return</span>
  84.  <span style="color:#75715e"># Git branch/tag, or name-rev if on detached head</span>
  85.  local GIT_LOCATION<span style="color:#f92672">=</span><span style="color:#e6db74">${</span><span style="color:#66d9ef">$(</span>git symbolic-ref -q HEAD <span style="color:#f92672">||</span> git name-rev --name-only --no-undefined --always HEAD<span style="color:#66d9ef">)</span>#(refs/heads/|tags/)<span style="color:#e6db74">}</span>
  87.  local AHEAD<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;%{</span>$fg<span style="color:#e6db74">[red]%}⇡NUM%{</span>$reset_color<span style="color:#e6db74">%}&#34;</span>
  88.  local BEHIND<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;%{</span>$fg<span style="color:#e6db74">[cyan]%}⇣NUM%{</span>$reset_color<span style="color:#e6db74">%}&#34;</span>
  89.  local MERGING<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;%{</span>$fg<span style="color:#e6db74">[magenta]%}⚡︎%{</span>$reset_color<span style="color:#e6db74">%}&#34;</span>
  90.  local UNTRACKED<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;%{</span>$fg<span style="color:#e6db74">[red]%}●%{</span>$reset_color<span style="color:#e6db74">%}&#34;</span>
  91.  local MODIFIED<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;%{</span>$fg<span style="color:#e6db74">[yellow]%}●%{</span>$reset_color<span style="color:#e6db74">%}&#34;</span>
  92.  local STAGED<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;%{</span>$fg<span style="color:#e6db74">[green]%}●%{</span>$reset_color<span style="color:#e6db74">%}&#34;</span>
  94.  local -a DIVERGENCES
  95.  local -a FLAGS
  97.  local NUM_AHEAD<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;</span><span style="color:#66d9ef">$(</span>git log --oneline @<span style="color:#f92672">{</span>u<span style="color:#f92672">}</span>.. 2&gt; /dev/null | wc -l | tr -d <span style="color:#e6db74">&#39; &#39;</span><span style="color:#66d9ef">)</span><span style="color:#e6db74">&#34;</span>
  98.  <span style="color:#66d9ef">if</span> <span style="color:#f92672">[</span> <span style="color:#e6db74">&#34;</span>$NUM_AHEAD<span style="color:#e6db74">&#34;</span> -gt <span style="color:#ae81ff">0</span> <span style="color:#f92672">]</span>; <span style="color:#66d9ef">then</span>
  99.    DIVERGENCES<span style="color:#f92672">+=(</span> <span style="color:#e6db74">&#34;</span><span style="color:#e6db74">${</span>AHEAD//NUM/$NUM_AHEAD<span style="color:#e6db74">}</span><span style="color:#e6db74">&#34;</span> <span style="color:#f92672">)</span>
  100.  <span style="color:#66d9ef">fi</span>
  102.  local NUM_BEHIND<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;</span><span style="color:#66d9ef">$(</span>git log --oneline [email protected]<span style="color:#f92672">{</span>u<span style="color:#f92672">}</span> 2&gt; /dev/null | wc -l | tr -d <span style="color:#e6db74">&#39; &#39;</span><span style="color:#66d9ef">)</span><span style="color:#e6db74">&#34;</span>
  103.  <span style="color:#66d9ef">if</span> <span style="color:#f92672">[</span> <span style="color:#e6db74">&#34;</span>$NUM_BEHIND<span style="color:#e6db74">&#34;</span> -gt <span style="color:#ae81ff">0</span> <span style="color:#f92672">]</span>; <span style="color:#66d9ef">then</span>
  104.    DIVERGENCES<span style="color:#f92672">+=(</span> <span style="color:#e6db74">&#34;</span><span style="color:#e6db74">${</span>BEHIND//NUM/$NUM_BEHIND<span style="color:#e6db74">}</span><span style="color:#e6db74">&#34;</span> <span style="color:#f92672">)</span>
  105.  <span style="color:#66d9ef">fi</span>
  107.  local GIT_DIR<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;</span><span style="color:#66d9ef">$(</span>git rev-parse --git-dir 2&gt; /dev/null<span style="color:#66d9ef">)</span><span style="color:#e6db74">&#34;</span>
  108.  <span style="color:#66d9ef">if</span> <span style="color:#f92672">[</span> -n $GIT_DIR <span style="color:#f92672">]</span> <span style="color:#f92672">&amp;&amp;</span> test -r $GIT_DIR/MERGE_HEAD; <span style="color:#66d9ef">then</span>
  109.    FLAGS<span style="color:#f92672">+=(</span> <span style="color:#e6db74">&#34;</span>$MERGING<span style="color:#e6db74">&#34;</span> <span style="color:#f92672">)</span>
  110.  <span style="color:#66d9ef">fi</span>
  112.  <span style="color:#66d9ef">if</span> <span style="color:#f92672">[[</span> -n <span style="color:#66d9ef">$(</span>git ls-files --other --exclude-standard 2&gt; /dev/null<span style="color:#66d9ef">)</span> <span style="color:#f92672">]]</span>; <span style="color:#66d9ef">then</span>
  113.    FLAGS<span style="color:#f92672">+=(</span> <span style="color:#e6db74">&#34;</span>$UNTRACKED<span style="color:#e6db74">&#34;</span> <span style="color:#f92672">)</span>
  114.  <span style="color:#66d9ef">fi</span>
  116.  <span style="color:#66d9ef">if</span> ! git diff --quiet 2&gt; /dev/null; <span style="color:#66d9ef">then</span>
  117.    FLAGS<span style="color:#f92672">+=(</span> <span style="color:#e6db74">&#34;</span>$MODIFIED<span style="color:#e6db74">&#34;</span> <span style="color:#f92672">)</span>
  118.  <span style="color:#66d9ef">fi</span>
  120.  <span style="color:#66d9ef">if</span> ! git diff --cached --quiet 2&gt; /dev/null; <span style="color:#66d9ef">then</span>
  121.    FLAGS<span style="color:#f92672">+=(</span> <span style="color:#e6db74">&#34;</span>$STAGED<span style="color:#e6db74">&#34;</span> <span style="color:#f92672">)</span>
  122.  <span style="color:#66d9ef">fi</span>
  124.  local -a GIT_INFO
  125.  GIT_INFO<span style="color:#f92672">+=(</span> <span style="color:#e6db74">&#34;\033[38;5;15m±&#34;</span> <span style="color:#f92672">)</span>
  126.  <span style="color:#f92672">[</span> -n <span style="color:#e6db74">&#34;</span>$GIT_STATUS<span style="color:#e6db74">&#34;</span> <span style="color:#f92672">]</span> <span style="color:#f92672">&amp;&amp;</span> GIT_INFO<span style="color:#f92672">+=(</span> <span style="color:#e6db74">&#34;</span>$GIT_STATUS<span style="color:#e6db74">&#34;</span> <span style="color:#f92672">)</span>
  127.  <span style="color:#f92672">[[</span> <span style="color:#e6db74">${#</span>DIVERGENCES[@]<span style="color:#e6db74">}</span> -ne <span style="color:#ae81ff">0</span> <span style="color:#f92672">]]</span> <span style="color:#f92672">&amp;&amp;</span> GIT_INFO<span style="color:#f92672">+=(</span> <span style="color:#e6db74">&#34;</span><span style="color:#e6db74">${</span>(j::)DIVERGENCES<span style="color:#e6db74">}</span><span style="color:#e6db74">&#34;</span> <span style="color:#f92672">)</span>
  128.  <span style="color:#f92672">[[</span> <span style="color:#e6db74">${#</span>FLAGS[@]<span style="color:#e6db74">}</span> -ne <span style="color:#ae81ff">0</span> <span style="color:#f92672">]]</span> <span style="color:#f92672">&amp;&amp;</span> GIT_INFO<span style="color:#f92672">+=(</span> <span style="color:#e6db74">&#34;</span><span style="color:#e6db74">${</span>(j::)FLAGS<span style="color:#e6db74">}</span><span style="color:#e6db74">&#34;</span> <span style="color:#f92672">)</span>
  129.  GIT_INFO<span style="color:#f92672">+=(</span> <span style="color:#e6db74">&#34;\033[38;5;15m</span>$GIT_LOCATION<span style="color:#e6db74">%{</span>$reset_color<span style="color:#e6db74">%}&#34;</span> <span style="color:#f92672">)</span>
  130.  echo <span style="color:#e6db74">&#34;</span><span style="color:#e6db74">${</span>(j: :)GIT_INFO<span style="color:#e6db74">}</span><span style="color:#e6db74">&#34;</span>
  132. <span style="color:#f92672">}</span>
  134. <span style="color:#75715e"># Use ❯ as the non-root prompt character; # for root</span>
  135. <span style="color:#75715e"># Change the prompt character color if the last command had a nonzero exit code</span>
  136. PS1<span style="color:#f92672">=</span><span style="color:#e6db74">&#39;
  137. </span><span style="color:#e6db74">$(ssh_info)%{$fg[magenta]%}%~%u $(git_info)
  138. </span><span style="color:#e6db74">%(?.%{$fg[blue]%}.%{$fg[red]%})%(!.#.❯)%{$reset_color%} &#39;</span>
  139. </code></pre></div><p>As with the <a href="/2012/12/30/my_git_prompt_for_zsh.html">original</a> version of this prompt, I hope this prompt is as useful and as big of a time saver for you as it is for me, and I&rsquo;d love to hear your thoughts about it!</p>
  140. ]]>
  141.    </content>
  142.  </entry><entry>
  143.    <title>Controlling Whitespace and Empty Lines in Jekyll</title>
  144.    <link rel="alternate" type="text/html" href="" />
  145.    <id>,2017:/2017/05/29/controlling_whitespace_and_empty_lines_in_jekyll.html</id>
  146.    <published>2017-05-29T00:00:00-05:00</published>
  147.    <updated>2017-05-29T00:00:00-05:00</updated>
  148.    <author>
  149.      <name>Josh Dick</name>
  150.      <uri></uri>
  151.    </author>
  152.    <content type="html" xml:lang="en">
  153.        <![CDATA[<blockquote>Jekyll-generated code can be pretty, too.</blockquote><blockquote>
  154. <p><strong>NOTE: This post will be obsolete soon.</strong></p>
  155. <p><a href="">Proper whitespace control</a> was <a href="">added</a> to Liquid 4. Liquid 4 has now been <a href="">added to Jekyll</a>, though it&rsquo;s not part of an official Jekyll release (yet.)</p>
  156. <p>This post applies to Jekyll 3.4.3 and earlier, which use earlier versions of Liquid.</p>
  157. <p><em>May 29, 2017</em></p>
  158. </blockquote>
  159. <h2 id="the-problem">The Problem</h2>
  160. <p>This blog is powered by the <a href="">Jekyll</a> static site generator, which internally uses <a href="">Liquid Markup</a> for templating.</p>
  161. <p>I noticed that Jekyll-generated output contains unwanted empty lines when there are corresponding Liquid template lines in the source code that wouldn&rsquo;t otherwise produce visible output.</p>
  162. <p>This example from <a href="">Liquid&rsquo;s whitespace control documentation</a> illustrates the problem:</p>
  163. <p><strong>Liquid Input</strong></p>
  164. <pre><code class="language-liquid" data-lang="liquid">{% assign username = &quot;John G. Chalmers-Smith&quot; %}
  165. {% if username and username.size &gt; 10 %}
  166.  Wow, {{ username }}, you have a long name!
  167. {% else %}
  168.  Hello there!
  169. {% endif %}
  170. </code></pre><p><strong>Generated Output</strong></p>
  171. <pre><code>
  173. Wow, John G. Chalmers-Smith, you have a long name!
  175. </code></pre><p>The empty lines are undesirable since they are unnecessary and they make the generated output uglier.</p>
  176. <h2 id="the-solution">The Solution</h2>
  177. <p>Here&rsquo;s my solution for removing empty lines from Jekyll-generated code.</p>
  178. <ol>
  179. <li>Add the following Jekyll plugin by creating a file named <code>_plugins/regex_filter.rb</code> with the following contents:</li>
  180. </ol>
  181. <div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-ruby" data-lang="ruby"><span style="color:#75715e">#</span>
  182. <span style="color:#66d9ef">module</span> Jekyll
  183.  <span style="color:#66d9ef">module</span> RegexFilter
  184.    <span style="color:#66d9ef">def</span> <span style="color:#a6e22e">replace_regex</span>(input, reg_str, repl_str)
  185.      re <span style="color:#f92672">=</span> <span style="color:#66d9ef">Regexp</span><span style="color:#f92672">.</span>new reg_str
  187.      <span style="color:#75715e"># This will be returned</span>
  188.      input<span style="color:#f92672">.</span>gsub re, repl_str
  189.    <span style="color:#66d9ef">end</span>
  190.  <span style="color:#66d9ef">end</span>
  191. <span style="color:#66d9ef">end</span>
  193. <span style="color:#66d9ef">Liquid</span><span style="color:#f92672">::</span><span style="color:#66d9ef">Template</span><span style="color:#f92672">.</span>register_filter(<span style="color:#66d9ef">Jekyll</span><span style="color:#f92672">::</span><span style="color:#66d9ef">RegexFilter</span>)
  194. </code></pre></div><ol start="2">
  195. <li>Use the following pattern in your Liquid templates:</li>
  196. </ol>
  197. <pre><code class="language-liquid" data-lang="liquid">{% capture output %}
  198. Content starts here
  199. Here are lines with more content
  200. {% if false %}This generates a blank line that will be stripped from the output{% endif %}
  201. Content ends here
  202. {% endcapture %}{{ output | replace_regex: '^\s*$\n', ''}}
  203. </code></pre><ol start="3">
  204. <li>That&rsquo;s it!</li>
  205. </ol>
  206. <p>The idea is that a block of template-generated output is captured within the template itself, then fed to a custom Liquid filter (the Jekyll plugin) that removes all empty lines using a regular expression.</p>
  207. <p>The <code>{% raw %}{% endcapture %}{% endraw %}</code> and <code>{% raw %}{% output %}{% endraw %}</code> Liquid tags appear on the same line to prevent an empty line from appearing at the top of the generated output.</p>
  208. <p>You can chain multiple invocations of the <code>replace_regex</code> filter together if you want to perform multiple distinct whitespace transformations.</p>
  209. <p>This is a simple idea, but I think it helps make Jekyll-generated code more pleasant to look at.</p>
  210. ]]>
  211.    </content>
  212.  </entry><entry>
  213.    <title>Understanding iOS Universal Links</title>
  214.    <link rel="alternate" type="text/html" href="" />
  215.    <id>,2017:/2017/01/08/understanding_ios_universal_links.html</id>
  216.    <published>2017-01-08T00:00:00-05:00</published>
  217.    <updated>2017-01-08T00:00:00-05:00</updated>
  218.    <author>
  219.      <name>Josh Dick</name>
  220.      <uri></uri>
  221.    </author>
  222.    <content type="html" xml:lang="en">
  223.        <![CDATA[<blockquote>When &ldquo;Open In App&rdquo; stubbornly refuses to keep its promise.</blockquote><p><a href="">Universal Links</a> first appeared in iOS 9. According to Apple&rsquo;s <a href="">Supporting Universal Links</a> document:</p>
  224. <blockquote>
  225. <p>When you support universal links, iOS 9 users can tap a link to your website and get seamlessly redirected to your installed app without going through Safari. If your app isn&rsquo;t installed, tapping a link to your website opens your website in Safari.</p>
  226. </blockquote>
  227. <p>This is a great idea in principle, since one URL can serve two purposes without needing to use custom URL schemes, but Universal links were not working as advertised for me and I figured out why. If you are having problems getting Universal links to behave as expected, I hope this article can help.</p>
  228. <h2 id="the-problem">The Problem</h2>
  229. <h3 id="open-in-app-opens-an-apps-app-store-page-instead-of-the-app">&ldquo;Open In App&rdquo; Opens an app&rsquo;s App Store page instead of the app</h3>
  230. <p>I use <a href="">imgur</a> and have its associated app installed on my phone, but I noticed that the &ldquo;Open In App&rdquo; buttons that appear on its mobile site (highlighted below) all loaded the App Store page for the imgur app instead of loading the content inside the imgur app as the buttons claimed they would.</p>
  231. <p><img src="/post_assets/2017/01/imgur_open_in_app_buttons.png" alt="imgur&rsquo;s &ldquo;Open in App&rdquo; buttons"></p>
  232. <p><img src="/post_assets/2017/01/imgur_app_store_page.png" alt="imgur&rsquo;s App Store page"></p>
  233. <p>I figured there was some glitch with the buttons that was mistakenly redirecting me to the App Store. Imgur&rsquo;s App Store page showed the &ldquo;Open&rdquo; button that normally appears when you look at an App Store page for an installed app, so for a while it never occurred to me to press the button since I figured it would just open the app to its default state, just like it does when manually viewing its App Store page by searching for it in the App Store.</p>
  234. <p>I was wrong.</p>
  235. <p>It turns out that <strong>tapping the Open button on an app&rsquo;s App Store page after being redirected to it by tapping a Universal Link will open the linked content in-app, rather than the default/front page of the app.</strong></p>
  236. <p>There is no visual indication that App Store page &ldquo;Open&rdquo; buttons have different behaviors when being redirected from a Universal Link versus browsing the App Store manually, even though this is clearly the case.</p>
  237. <p>Regardless, I expected &ldquo;Open In App&rdquo; to actually load the linked content in-app and not to add an extra step of loading an app&rsquo;s App Store page.</p>
  238. <h2 id="the-realization">The Realization</h2>
  239. <p>After doing some Internet digging, bullet point 4 of <a href="">this StackOverflow answer</a> shed some light on the situation.</p>
  240. <p>First, some terminology: I will refer to a Universal Link as <strong>enabled</strong> if tapping it causes content to load in-app, and <strong>disabled</strong> if tapping it causes content to load in a web page or causes an App Store page to open.</p>
  241. <p>It turns out that different URL paths under a single domain name can be independently set to have their corresponding Universal Link behavior be enabled/disabled depending on how the developer configured them (see the &ldquo;Creating and Uploading the Association File&rdquo; section of Apple&rsquo;s <a href="">Supporting Universal Links</a> document), and that <strong>the per-Universal Link setting stays in effect until it is changed again</strong>.</p>
  242. <p>This means that the instructions below may need to be repeated multiple times for a single site.</p>
  243. <p>Another factor that adds to the confusion is that there is no way to tell whether a given Universal Link is enabled/disabled other than tapping it to see what its behavior currently is.</p>
  244. <h2 id="the-solution">The Solution</h2>
  245. <h3 id="enabling-a-universal-link">Enabling a Universal Link</h3>
  246. <p>If tapping a Universal Link currently opens a web or App Store page as described above but you want the link to cause content to load in-app, that means the Universal Link is currently disabled. Here&rsquo;s how to enable it:</p>
  247. <ol>
  248. <li>
  249. <p>Try pulling down/scrolling up on the web site when the page view is already scrolled all the way to the top to reveal an <code>Open in the [App Name] App</code> banner as pictured below:</p>
  250. <p><img src="/post_assets/2017/01/imgur_open_in_app_banner.png" alt="imgur&rsquo;s App Store page"></p>
  251. <p>Tapping the banner will enable the Universal Link and cause the content to load in-app.</p>
  252. </li>
  253. <li>
  254. <p>If no banner appears as shown above, tap and hold on the Universal Link until a dialog with buttons appears. If you scroll through the buttons, one should say <code>Open in &quot;[App Name]&quot;</code> as pictured below:</p>
  255. <p><img src="/post_assets/2017/01/imgur_open_in_app_button.png" alt="imgur&rsquo;s App Store page"></p>
  256. <p>Tapping the <code>Open in &quot;[App Name]&quot;</code> button will enable the Universal Link and cause the content to load in-app.</p>
  257. </li>
  258. </ol>
  259. <p>Once the Universal Link is enabled (content loads in-app), it will <strong>always load in-app in the future</strong> unless you [re]disable the Universal Link as described below.</p>
  260. <p>Note that when tapping a disabled Universal Link causes a redirection to an app&rsquo;s App Store page, tapping the &ldquo;Open&rdquo; button on that page <strong>will cause content to load in-app that one time, and will not enable that Universal Link for future use as described above.</strong></p>
  261. <h3 id="disabling-a-universal-link">Disabling a Universal Link</h3>
  262. <p>If tapping a Universal Link currently causes content content to load in-app but you want the link to open a web (or App Store) page, that means the Universal Link is currently enabled. Here&rsquo;s how to disable it:</p>
  263. <p>When content has loaded in-app after tapping a Universal Link, you should see some text at the very top-right of the screen in the iOS status bar with the domain name of the page whose Universal Link redirected you to that app, as pictured below:</p>
  264. <p><img src="/post_assets/2017/01/imgur_status_bar_link.png" alt="imgur&rsquo;s App Store page"></p>
  265. <p>Tapping that text will cause the content to open in  a web (or App Store) page and will disable the Universal Link that opened the app.</p>
  266. <p>Once the Universal Link is disabled (content doesn&rsquo;t load in-app), content will <strong>never load in-app in the future</strong> unless you [re]enable the Universal Link as described above.</p>
  267. <p>If you want to view content from an enabled Universal Link on the web after its content loads in-app just one time/without disabling the Universal Link entirely, <strong>don&rsquo;t tap the Status Bar text</strong>; instead, just switch back to your web browser.</p>
  268. <h3 id="a-note-on-app-store-page-redirection">A Note on App Store Page Redirection</h3>
  269. <p>The behavior of disabled Universal Links causing redirections to an App Store page instead of loading content in a web page appears to be web site-specific.</p>
  270. <p>In the case of my imgur example, the App Store redirection seems to be functionality that imgur explicitly implemented to try to steer users towards using their app instead of their web site, since tapping a disabled Universal Link on imgur&rsquo;s web site does appear to load another page on the web site for a split second before redirecting to imgur&rsquo;s App Store page. In other words, the Universal Link correctly opens imgur&rsquo;s web site as expected, which itself then redirects to imgur&rsquo;s App Store page (where the &ldquo;Open&rdquo; button would cause the content to load in-app one time as described above.) It&rsquo;s possible that other sites would load web content in a web page as expected when tapping a disabled Universal Link, rather than redirecting users to an App Store page as is the case for imgur.</p>
  271. <h2 id="conclusion">Conclusion</h2>
  272. <p>The mechanisms built in to iOS for enabling and disabling Universal Links are difficult to understand, and the fact that settings are sticky/permanent and can independently vary across given Universal Links under a single domain is not made apparent whatsoever by the UIs iOS provides around this feature.</p>
  273. <p>This confusion is compounded when developers implement behavior that causes web sites to open App Store pages when tapping disabled Universal Links (as imgur seems to have done), causing content not to open in a web view as expected, despite the fact that the Universal Link is disabled.</p>
  274. <p>&ldquo;Open in App&rdquo; links behaving differently than I expected was a large source of frustration for me when browsing the web on iOS. Given how confusing this issue was to understand, solve, and then write about, I hope this article was helpful.</p>
  275. ]]>
  276.    </content>
  277.  </entry><entry>
  278.    <title>An Event Apart Boston 2015</title>
  279.    <link rel="alternate" type="text/html" href="" />
  280.    <id>,2015:/2015/06/28/an_event_apart_boston_2015.html</id>
  281.    <published>2015-06-28T00:00:00-05:00</published>
  282.    <updated>2015-06-28T00:00:00-05:00</updated>
  283.    <author>
  284.      <name>Josh Dick</name>
  285.      <uri></uri>
  286.    </author>
  287.    <content type="html" xml:lang="en">
  288.        <![CDATA[<blockquote>My notes from An Event Apart, &ldquo;the design conference for people who make websites&rdquo;.</blockquote><p><img src="/post_assets/2015/06/aea_boston_2015_bacon_cupcake.jpg" alt="Bacon Cupcake"></p>
  289. <h1 id="introduction">Introduction</h1>
  290. <p>I had the privilege of attending An Event Apart, &ldquo;the design conference for people who make websites&rdquo;, for the fourth time. My notes from <a href="">An Event Apart Boston 2015</a> follow this introduction. The notes are grouped by talk, in the order that each talk happened at the conference.</p>
  291. <p>If you&rsquo;re interested, my notes from An Event Apart Boston <a href="/2012/08/19/an_event_apart_boston_2012.html">2014</a> are also available.</p>
  292. <h1 id="day-1-5112015">Day 1: 5/11/2015</h1>
  293. <h2 id="jeffrey-zeldman---the-fault-dear-brutus-or-career-advice-from-a-cranky-old-man-zeldmancomhttpwwwzeldmancom-bull-zeldmanhttpstwittercomzeldman">Jeffrey Zeldman - The Fault, Dear Brutus (or: Career Advice From a Cranky Old Man) (<a href=""></a> • <a href="">@zeldman</a>)</h2>
  294. <ul>
  295. <li>&ldquo;When I get stuck in a rut, I decorate it.&rdquo;</li>
  296. <li>Work never sells itself. You need a strategy to sell.</li>
  297. <li>&ldquo;Every client wants something nobody&rsquo;s done before that has worked at least three times for other people.&rdquo;</li>
  298. <li>In big companies, politics trumps work.</li>
  299. <li>Attitude trumps work in most companies. Being indignant is not a good career move; attitude is everything.</li>
  300. <li>First impressions are forever.</li>
  301. <li>You are what stands between you and success: &ldquo;We have met the enemy and he is us.&rdquo; -Pogo</li>
  302. <li>Dare to speak. Unlock your inner voice! (Blogging, <a href="">Dribbble</a>, <a href="">Behance</a>, <a href="">GitHub</a>, <a href="">Codepen</a>, etc&hellip;) Blogs and side projects can show how you think and what you do, even if your regular work can&rsquo;t (or you&rsquo;re not allowed to share your regular work.)</li>
  303. <li>&ldquo;When you pick a typeface, your design is halfway done.&rdquo;</li>
  304. <li>Don&rsquo;t wait for someone to hand you your dream job or project &ndash; make your own.</li>
  305. </ul>
  306. <hr>
  307. <h2 id="jon-hicks---icon-design-process-zeldmancomhttphicksdesigncouk-bull-hicksdesignhttpstwittercomhicksdesign">Jon Hicks - Icon Design Process (<a href=""></a> • <a href="">@hicksdesign</a>)</h2>
  308. <ul>
  309. <li>Never use color alone to signify meaning.</li>
  310. <li>Why make your own icons instead of using a royalty-free icon set?
  311. <ul>
  312. <li>Not the right size</li>
  313. <li>Not the right style</li>
  314. <li>Too many &lsquo;spare&rsquo; icons</li>
  315. <li>Not the right icons (for a specialized application, like GitHub)</li>
  316. </ul>
  317. </li>
  318. <li>There are two main types of icons: iconic and symbolic. Iconic icons resemble real things; symbolic icons don&rsquo;t (their meaning is learned.)</li>
  319. <li>Iconic icons are easier/faster to recognize than symbolic icons.</li>
  320. <li>Embrace conventions! Don&rsquo;t use a welcome mat icon to represent &ldquo;home&rdquo;.</li>
  321. <li><a href="">The Noun Project</a></li>
  322. <li>Research local knowledge: A piggy bank, a thumbs up, and an owl have different meanings for different cultures.</li>
  323. <li>It&rsquo;s possible to be <em>too</em> simple: Icons for a padlock, a shopping bag, and a 10-ton weight can look more or less identical in the absence of context (text labels) or extra visual details.</li>
  324. <li>Whatever you use, decide:
  325. <ul>
  326. <li>Size(s)</li>
  327. <li>Style</li>
  328. <li>Final Export Format (SVG)</li>
  329. </ul>
  330. </li>
  331. <li>Work on all icons together; use a grid to size/align/balance all icons.</li>
  332. <li>Antialiasing can get in the way sometimes; an odd-number-sized grid can help with this.</li>
  333. <li>Optimize SVG files with <a href="">svgo</a></li>
  334. <li>Icon fonts vs. SVG:
  335. <ul>
  336. <li>Why use icon fonts?
  337. <ul>
  338. <li>Scalable
  339. <li>Small files</li>
  340. <li>Easily styled with CSS No sprites</li>
  341. <li>Supported in IE4+!</li>
  342. </ul>
  343. </li>
  344. <li>Why not?
  345. <ul>
  346. <li>Fiddly process</li>
  347. <li>No meaning</li>
  348. <li>Only monochrome</li>
  349. <li>No font = no joy</li>
  350. <li>Rendering Inconsistencies</li>
  351. <li>No meaning?</li>
  352. </ul>
  353. </li>
  354. </ul>
  355. </li>
  356. <li><a href="">Grumpicon</a>: Generate cross-browser iconsets from SVG, with appropriate fallbacks.</li>
  357. <li>SVG elements can reference each other, which allows a single SVG path to be reused and thus drawn with different CSS styles/sizes/etc. without duplicating the path.</li>
  358. </ul>
  359. <hr>
  360. <h2 id="sarah-parmenter---designing-for-social-behavior-sazzycoukhttpwwwsazzycouk-bull-sazzyhttpstwittercomsazzy">Sarah Parmenter - Designing for Social Behavior (<a href=""></a> • <a href="">@sazzy</a>)</h2>
  361. <ul>
  362. <li>&ldquo;Whenever I hear the phrase &lsquo;Social Media&rsquo;, I think &lsquo;Social Medi<!-- raw HTML omitted -->blah<!-- raw HTML omitted -->&rsquo; instead.&rdquo;</li>
  363. <li>Social media is a tool to make <em>something</em> happen.</li>
  364. <li>An effective social media campaign is based on the psychology of social behaviors, <em>not</em> current technology. &ndash;<a href="">Media Psychology Research Center</a></li>
  365. <li>The basic social ecosystem (your persona and tone of voice) includes 4 channels:
  366. <ul>
  367. <li>Publishing channels</li>
  368. <li>Aspirational/inspirational</li>
  369. <li>Support channels</li>
  370. <li>Follow up channels</li>
  371. </ul>
  372. </li>
  373. <li>To survive, a [social] mobile app must have razor-sharp focus on doing just one thing.</li>
  374. <li>With Facebook advertising, <strong>you</strong> are the product: You need to pay to access the followers that you&rsquo;ve worked to build up.</li>
  375. <li>What people use &ldquo;liking&rdquo; for:
  376. <ul>
  377. <li>Acknowledging that someone has seen/read something without explicitly leaving a comment</li>
  378. <li>Using as a &ldquo;read&rdquo; flag, like e-mail</li>
  379. </ul>
  380. </li>
  381. <li>Why do people comment on a photo that already has 129,000 previous comments? Tribe behavior. It&rsquo;s like shouting at a sports event. #aeabos &ndash;<a href="">@zeldman</a></li>
  382. <li>Tribe mentality is a key ingredient to both online and offline design.</li>
  383. <li>Give anyone long enough, and they&rsquo;ll work out how to game the system.</li>
  384. <li>Social media calls for authenticity: it cannot be faked.</li>
  385. <li>The lightbulb moment: Don&rsquo;t do the safe/expected thing, be prepared to have difficult conversations. If you can&rsquo;t, it will limit your ability to do good work.</li>
  386. </ul>
  387. <hr>
  388. <h2 id="josh-clark---magical-ux-and-the-internet-of-things-globalmoxiecomhttpglobalmoxiecom-bull-globalmoxiehttpstwittercomglobalmoxie">Josh Clark - Magical UX and the Internet of Things (<a href=""></a> • <a href="">@globalmoxie</a>)</h2>
  389. <h3 id="act-i-magic--technology">Act I: Magic &amp; Technology</h3>
  390. <ul>
  391. <li>&ldquo;Any sufficiently advanced technology is indistinguishable from magic.&rdquo; &ndash;Arthur C. Clarke</li>
  392. <li>&ldquo;One goal: The computer disappears into the environment.&rdquo; &ndash;Alan Kay</li>
  393. <li>The phone is the first Internet of Things device for everyone (sensors + smarts + connectivity.)</li>
  394. <li>Mobile phones bring computing power to immobile objects.</li>
  395. <li>Embed smartphone brains in anything. Example: Nappy Notifier: Get a push notification when your baby&rsquo;s diaper is wet.</li>
  396. <li>&ldquo;We have centuries of experiencing imagining what objects could do for us if they were just&hellip;smarter.&rdquo;</li>
  397. <li><a href=""></a> and <a href=""></a> connect to <a href="">ifttt</a> and <a href="">Zapier</a></li>
  398. </ul>
  399. <h3 id="act-ii-physical-meets-digital">Act II: Physical Meets Digital</h3>
  400. <ul>
  401. <li>Physical interaction with a digital API.</li>
  402. <li>The world is the interface&hellip;like it always has been!</li>
  403. <li>The world is a data source. Example: Snapshot by Progressive Insurance/<a href="">Automatic</a> use cars&rsquo; OBD-II ports to collect data.</li>
  404. <li>The world is reactive &ndash; intentional interfaces that extend our will. Example: <a href="">Ares Sand Table</a></li>
  405. <li>The world is a big canvas.</li>
  406. <li>What if we stop focusing on wearables, and instead think about &ldquo;thereables&rdquo;, adding intelligence to objects that are already in the world? Why isn&rsquo;t your bed a sleep tracker, instead of something like a FitBit?</li>
  407. <li>The world has depth and mass. Physical objects can act together and be aware of each other across a digital space. Example: <a href="">MIT Thaw</a></li>
  408. <li>This is not a challenge of technology. It&rsquo;s a challenge of imagination.</li>
  409. </ul>
  410. <h3 id="act-iii-magic-imagined">Act III: Magic, Imagined</h3>
  411. <ul>
  412. <li>Google Glass asked, &ldquo;What can we do with technology on your face?&rdquo; It should have asked, &ldquo;What if this thing was magic?&rdquo;</li>
  413. <li>Design for the thing&rsquo;s essential thingness. Make things more like they are (and make ourselves more human), not just more technically impressive.</li>
  414. <li>Bank on illusion. Embrace misdirection. Example: Samsung&rsquo;s electric cooktop has flame-like LEDs since that gels with a user&rsquo;s mental model of a hot stove.</li>
  415. <li><a href="">Vessyl</a> has amazing technology but <a href="">doesn&rsquo;t actually add value</a>.</li>
  416. <li>Don&rsquo;t just add data; add insight. Can you imagine if every object in your house was giving you <a href="">constant status updates</a>?</li>
  417. <li>Expose as little technology as possible.</li>
  418. <li>Be a little bit ridiculous. Examples: <a href="">Sharknado + Philips Hue</a> and ThinkGeek&rsquo;s <a href="">Mega Stomp Battle</a>.</li>
  419. <li>&ldquo;The future of technology has always looked like a pretty toy to people comfortable with the past.&rdquo; &ndash;Benedict Evans</li>
  420. <li>People fear that magic always goes wrong: &ldquo;How smart does your bed have to be before you are afraid to go to sleep at night?&rdquo; &ndash;Rich Gold</li>
  421. <li>Build systems that are smart enough to know they&rsquo;re not smart enough.</li>
  422. <li>Make technology invisible and humane.</li>
  423. <li>It&rsquo;s not &ldquo;Can we?&quot;, it&rsquo;s &ldquo;How will we?&rdquo;</li>
  424. <li>The &ldquo;Internet of Things&rdquo; is not about the thing. The technology should amplify our humanity.</li>
  425. </ul>
  426. <hr>
  427. <h2 id="mat-marquis---smaller-faster-web-sites-matmarquiscomhttpwwwmatmarquiscom-bull-wiltohttpstwittercomwilto">Mat Marquis - Smaller, Faster Web Sites (<a href=""></a> • <a href="">@wilto</a>)</h2>
  428. <ul>
  429. <li>Users just want to keep their coffee off the floor, they don&rsquo;t care about the table.</li>
  430. <li>When we value convenience over craft, we&rsquo;re designing a web for ourselves, not for users.</li>
  431. <li>We&rsquo;re building the IKEA web: easy to build, but uncomfortable to use.</li>
  432. <li>20% of US users depend on smartphones almost exclusively for the Internet.</li>
  433. <li>Average page weight is 1944 KB &ndash; mostly images.</li>
  434. <li>The right image size(s) for the right device: Serve responsive images with the <code>srcset</code> attribute and the <code>&lt;picture&gt;</code> element.</li>
  435. <li>Use <a href="">picturefill</a> for legacy browsers that don&rsquo;t support the <code>&lt;picture&gt;</code> element.</li>
  436. <li>SVG is widely supported, but still doesn&rsquo;t work on Android &ndash; a huge number of Android devices still ship with 2.3 today!</li>
  437. <li>&ldquo;It seems every year one of us accidentally discovers another game-changing thing that SVG has been able to do since 1987.&rdquo; &ndash;@ScottJehl</li>
  438. <li>~14 KB included in initial TCP/IP connection, so critical CSS should be at the top of the page.
  439. <ul>
  440. <li><a href=""></a></li>
  441. <li><a href=""></a>
  442. <ul>
  443. <li>Can also use this to defer loading of webfonts.</li>
  444. </ul>
  445. </li>
  446. <li>Set a performance budget! Validate it with Grunt: <a href=""></a></li>
  447. </ul>
  448. </li>
  449. </ul>
  450. <hr>
  451. <h2 id="ethan-marcotte---laziness-in-the-time-of-responsive-design-ethanmarcottecomhttpethanmarcottecom-bull-beephttpstwittercombeep">Ethan Marcotte - Laziness in the Time of Responsive Design (<a href=""></a> • <a href="">@beep</a>)</h2>
  452. <ul>
  453. <li>Categories like &ldquo;tablet&rdquo; and &ldquo;mobile&rdquo; are so broad as to be completely unhelpful as they pertain to our work.</li>
  454. <li>&ldquo;My anxiety doesn&rsquo;t come from thinking about the future, but from wanting to control it.&rdquo; &ndash;Hugh Prather</li>
  455. <li>Stop trying to perfectly control rendering on every device and platform.</li>
  456. <li>Avoid describing ideal layouts in markup; it gives you more flexibility in the long run.</li>
  457. <li>&ldquo;Instead of solutions for problems, [systems] for solutions: for no problem is there an absolute solution. There is always a group of solutions, one of which is the best under certain conditions.&rdquo; &ndash;Karl Gerstner</li>
  458. <li>Making it fit is the baseline. How can we make it feel at home?</li>
  459. <li>Start designing from a network of small layout systems and scale up from there.</li>
  460. <li>Responsive navigation:
  461. <ul>
  462. <li>Off-canvas</li>
  463. <li>Off-canvas navigation triggered by &lsquo;the hamburger&rsquo; (&amp;#9776; → ☰) hasn&rsquo;t been as successful as most of us think.</li>
  464. <li>The hamburger&rsquo;s function is not always self-evident.</li>
  465. <li>We don&rsquo;t always need to have the default expectation that navigation should be concealed on mobile.</li>
  466. <li>We&rsquo;re shoving our mess under the bed that is the off-canvas hamburger navigation menu on mobile.</li>
  467. <li>A lot of the needless complexity we foist on our responsive navs comes from thinking about them as desktop-first.</li>
  468. </ul>
  469. </li>
  470. <li>We should look for opportunities to be just a little lazy &ndash; maybe it&rsquo;s about a conservation of effort.</li>
  471. <li>Design the transaction, not the interface.</li>
  472. <li>A well-crafted responsive design is device-agnostic.
  473. <ul>
  474. <li>&ldquo;There&rsquo;s more to devices than the size of their screens. A device-agnostic approach also takes into account infinite combinations of screen resolution, input method, browser capability, and connection speed.&rdquo; &ndash;Trent Walton</li>
  475. <li>&ldquo;Like cars designed to perform in extreme heat or on icy roads, websites should be built to face the reality of the web&rsquo;s inherent variability.&rdquo; &ndash;Trent Walton</li>
  476. </ul>
  477. </li>
  478. </ul>
  479. <hr>
  480. <h1 id="day-2-5122015">Day 2: 5/12/2015</h1>
  481. <h2 id="eric-meyer---designing-for-crisis-meyerwebcomhttpmeyerwebcom-bull-meyerwebhttpstwittercommeyerweb">Eric Meyer - Designing for Crisis (<a href=""></a> • <a href="">@meyerweb</a>)</h2>
  482. <ul>
  483. <li>&ldquo;You don&rsquo;t get to decide what your users will want to do on mobile. They do.&rdquo; &ndash;Karen McGrane</li>
  484. <li>Add another persona to your list: the user in crisis, who can barely think straight. (Example: Confusing, cluttered hospital web site.)</li>
  485. <li>Empathy is a core design skill.</li>
  486. <li>When <strong>usability testing</strong> a design for people in crisis, add <strong>confusion/annoyances</strong> to the page to suck up mental resources, to make sure the design still works. (Blurred text, shaky page, transposing text, etc.)</li>
  487. </ul>
  488. <hr>
  489. <h2 id="rachel-andrew---css-grid-layout-rachelandrewcoukhttprachelandrewcouk-bull-rachelandrewhttpstwittercomrachelandrew">Rachel Andrew - CSS Grid Layout (<a href=""></a> • <a href="">@rachelandrew</a>)</h2>
  490. <ul>
  491. <li>Seeing Flexbox as the silver bullet for layout issues is likely to lead us down another path of layout hacks.</li>
  492. <li>Flexbox is designed for things that can be represented as a single, unbroken line, not grids.</li>
  493. <li>CSS Grid Layout to the rescue: <a href=""></a></li>
  494. <li>CSS Grid Layout is useful as a prototyping tool even though browsers aren&rsquo;t [yet] ready to use it in production.</li>
  495. <li><a href="">Bootstrap</a> and similar frameworks rely on describing the layout in the markup.</li>
  496. <li>With CSS Grid Layout, we describe the layout in the CSS and can redefine that description at any breakpoint.</li>
  497. <li>We can even use CSS Grid Layout to recreate a Bootstrap-style 12-column grid, without needing to describe the grid in the markup.</li>
  498. <li>CSS Grid Layout allows cells to be spanned vertically, eliminating the need for nested grids.</li>
  499. </ul>
  500. <hr>
  501. <h2 id="brad-frost---atomic-design-bradfrostcomhttpbradfrostcom-bull-brad_frosthttpstwittercombrad_frost">Brad Frost - Atomic Design (<a href=""></a> • <a href="">@brad_frost</a>)</h2>
  502. <ul>
  503. <li>We&rsquo;re not designing pages, we&rsquo;re designing systems of components. &ndash;Stephen Hay</li>
  504. <li>Potential pitfalls with web frameworks:
  505. <ul>
  506. <li>One-size-fits-all</li>
  507. <li>Lookalike issues</li>
  508. <li>Might not do everything you need</li>
  509. <li>Compatibility with existing sites</li>
  510. <li>Subscribe to someone else&rsquo;s structure, naming, and style</li>
  511. </ul>
  512. </li>
  513. <li>☛ Atomic design = creating pattern library/style guide <strong>first</strong>, instead of cherrypicking patterns <strong>after</strong> design. @brad_frost #aeabos &ndash;<a href="">@zeldman</a></li>
  514. <li>Responsive deliverables should look a lot like fully-functioning Twitter Bootstrap-style systems custom tailored for your clients&rsquo; needs. -Dave Rupert</li>
  515. <li>Benefits of front-end style guides:
  516. <ul>
  517. <li>Promotes consistency and cohesion</li>
  518. <li>Easier to test</li>
  519. <li>Better workflow</li>
  520. <li>Creates a shared vocabulary</li>
  521. <li>Useful reference</li>
  522. <li>Future-friendly foundation</li>
  523. </ul>
  524. </li>
  525. <li>Getting started with style guides:
  526. <ul>
  527. <li><a href=""></a></li>
  528. <li><a href=""></a></li>
  529. <li><a href=""></a></li>
  530. <li><a href=""></a></li>
  531. </ul>
  532. </li>
  533. <li>Example style guides:
  534. <ul>
  535. <li><a href=""></a></li>
  536. <li><a href=""></a></li>
  537. <li><a href=""></a></li>
  538. <li><a href=""></a></li>
  539. </ul>
  540. </li>
  541. <li>Atomic design tool: <a href=""></a></li>
  542. <li>Frontend development is part of the design process.</li>
  543. <li>Collaboration and communication trump deliverables.</li>
  544. </ul>
  545. <hr>
  546. <h2 id="derek-featherstone---content-in-context-is-king-simplyaccessiblecomhttpsimplyaccessiblecom-bull-featherhttpstwittercomfeather">Derek Featherstone - Content in Context is King (<a href=""></a> • <a href="">@feather</a>)</h2>
  547. <ul>
  548. <li>Great experiences are heavily based on context.</li>
  549. <li>Context is often seen as &ldquo;the device someone is using&rdquo;, but context is actually:
  550. <ul>
  551. <li>Time</li>
  552. <li>Location</li>
  553. <li>Proximity</li>
  554. <li>Device</li>
  555. <li>State of mind</li>
  556. <li>Capabilities</li>
  557. <li>Activity</li>
  558. <li>Interests</li>
  559. <li>Interaction</li>
  560. </ul>
  561. </li>
  562. <li>Content priority changes with respect to time. Example: Showing a conference schedule front and center on its web page while the conference is actually occurring.</li>
  563. <li>Programmatically change content priority over time. This applies to almost any industry.</li>
  564. <li>Content priority changes with respect to location. Example: For a college web site, show directions to the college if you&rsquo;re not present on campus, or an internal campus map if you are.</li>
  565. <li>Content display also changes with respect to location. Example: Date picker starting on Sunday if you&rsquo;re in the US, Monday everywhere else.</li>
  566. <li>Content changes with respect to proximity.</li>
  567. <li>All saved context must be resettable.</li>
  568. </ul>
  569. <hr>
  570. <h2 id="kate-kiefer-lee---touchy-subjects-creating-content-for-sensitive-situations-katekieferleecomhttpkatekieferleecom-bull-katekieferhttpstwittercomkatekiefer">Kate Kiefer Lee - Touchy Subjects: Creating Content for Sensitive Situations (<a href=""></a> • <a href="">@katekiefer</a>)</h2>
  571. <ul>
  572. <li>Sensitive topics and industries:
  573. <ul>
  574. <li>health and medicine</li>
  575. <li>money and banking</li>
  576. <li>private information</li>
  577. <li>fundraising</li>
  578. <li>religion</li>
  579. <li>politics</li>
  580. </ul>
  581. </li>
  582. <li>Urgent messages:
  583. <ul>
  584. <li>error messages security notifications</li>
  585. <li>warnings and compliance alerts</li>
  586. <li>rejection notices</li>
  587. <li>apologies</li>
  588. </ul>
  589. </li>
  590. <li>Less urgent messages:
  591. <ul>
  592. <li>help docs</li>
  593. <li>customer service emails contact pages</li>
  594. <li>forms</li>
  595. <li>unsubscribe pages</li>
  596. <li>legal policies</li>
  597. </ul>
  598. </li>
  599. <li>Principles:
  600. <ul>
  601. <li>Be clear</li>
  602. <li>Get to the point</li>
  603. <li>Stay calm</li>
  604. <li>Be serious</li>
  605. <li>Accept responsibility</li>
  606. <li>Be nice</li>
  607. </ul>
  608. </li>
  609. <li>&ldquo;It is insight into human nature that is key to the communicator&rsquo;s skill. For whereas the writer is concerned with what he puts into his writings, the communicator is concerned with what the reader gets out of it.&rdquo; &ndash;William Bernbach</li>
  610. <li>&ldquo;A good teacher I know, Jenifer Auger, has a simple but effective technique for the writing classroom. When her students have blah voiceless writing, she makes them speak the following words to her before reading their text: &lsquo;Listen to me, I have something to tell you.'&rdquo; &ndash;Peter Elbow</li>
  611. <li>Read it out loud!</li>
  612. <li>Know when saying nothing is best: &ldquo;Brands are not people. Customers are not close friends. And boundaries need to be maintained.&rdquo;</li>
  613. <li>Pick the right tone to match the reader&rsquo;s feelings based on the content type.</li>
  614. <li>&ldquo;New Yorker: &ldquo;We screwed up.&rdquo; Airline: &ldquo;We apologize for any inconvenience this may have caused.&rdquo; Which apology is more effective? #aeabos&rdquo; &ndash;<a href="">@zeldman</a></li>
  615. <li>Legal documents can use plain language, as long as the tone is appropriate.</li>
  616. <li>Prepare for the worst ahead of time: Create templates that can be used for responding to unexpected situations, keeping in mind:
  617. <ul>
  618. <li>Possible content types (email, tweet, blog post, etc.)</li>
  619. <li>Apologize up front if necessary say what happens next</li>
  620. <li>Who the message will be from who needs to sign off</li>
  621. <li>Laws and other requirements</li>
  622. </ul>
  623. </li>
  624. <li>We don&rsquo;t want our users to say, &ldquo;Great content!&rdquo; Instead: &ldquo;I got what I needed; it wasn&rsquo;t that hard; and I&rsquo;m better off now.&rdquo;</li>
  625. <li><a href=""></a></li>
  626. </ul>
  627. <hr>
  628. <h2 id="chris-coyier---the-wonderful-world-of-svg-chriscoyiernethttpchriscoyiernet-bull-chriscoyierhttptwittercomchriscoyier">Chris Coyier - The Wonderful World of SVG (<a href=""></a> • <a href="">@chriscoyier</a>)</h2>
  629. <ul>
  630. <li>SVG is widely supported by browsers today, and is still not used nearly enough.</li>
  631. <li>There are only a handful of basic shapes.</li>
  632. <li>For simple graphics, SVG file size is smaller and the quality is higher (best of both worlds), but there is a practical complexity limit.</li>
  633. <li>Practically any vector art can be converted to SVG.</li>
  634. <li>You can use an SVG file as the value of the <code>src</code> attribute in an <code>&lt;img /&gt;</code> tag, inline in the HTML, or referenced with <code>url()</code> in CSS.</li>
  635. <li>Why use SVG?
  636. <ul>
  637. <li>Resolution independent</li>
  638. <li>Use as a system</li>
  639. <li>Design possibilities</li>
  640. </ul>
  641. </li>
  642. <li>Why send pixel data when you can send geometry? Math is more efficient, let your powerful computer draw the thing.</li>
  643. <li>SVG is pretty efficient by itself, but can still be heavily optimized.
  644. <ul>
  645. <li>Server-side <code>gzip</code> works very well since SVG has lots of repetitive strings.</li>
  646. <li><a href="">svgo optimizer</a></li>
  647. </ul>
  648. </li>
  649. <li>SVG icons
  650. <ul>
  651. <li>An SVG icon system ensures that all icons are served via a single HTTP request, and makes icons easy to use.</li>
  652. <li><a href=""></a></li>
  653. <li>Why use SVG icons?
  654. <ol>
  655. <li>Vector!
Typically sharper than icon fonts because of non-text anti-aliasing.</li>
  656. <li>Easy multi-color! More CSS control than any other method.</li>
  657. <li>Animate!
Easy to apply transitions and animations.</li>
  658. <li>Script away!
Everything is in the DOM.</li>
  659. <li>Better accessibility!
Fool-proof, once you set it up well.</li>
  660. <li>Better semantics!
<code>&lt;svg&gt;</code> = &ldquo;image&rdquo; / <code>&lt;span&gt;</code> = &ldquo;nothing&rdquo;</li>
  661. <li>Ease of use! Easy to manage individual icons, instant build processes.</li>
  662. </ol>
  663. </li>
  664. </ul>
  665. </li>
  666. <li>SVG can be animated with both CSS and JavaScript.</li>
  667. <li>JavaScript libraries for working with SVG (all have slightly different capabilities, approaches, and focuses):
  668. <ul>
  669. <li><a href="">Snap.svg</a> - jQuery for SVG - kinda like newer Raphaël</li>
  670. <li><a href="">Greensock(GSAP)</a> - does some cool normalization stuff too</li>
  671. <li><a href="">Velocity.js</a></li>
  672. <li><a href="">SVG.js</a></li>
  673. <li><a href="">D3</a>
- data powerhouse</li>
  674. </ul>
  675. </li>
  676. <li>SVG is pretty great at charting. It doesn&rsquo;t have charting-specific features, but it has features that lend themselves well to charting.
  677. <ul>
  678. <li><a href="">amCharts</a></li>
  679. <li><a href="">Chartist.js</a></li>
  680. </ul>
  681. </li>
  682. <li>Clipping and masking</li>
  683. <li>Huge list of information about SVG: <a href=""></a></li>
  684. </ul>
  685. <hr>
  686. <h1 id="conclusion">Conclusion</h1>
  687. <p>To me, the concept of responsive web design means first and foremost that web sites should be able to adapt themselves for optimal viewing across any type of device. Implementing responsive designs is made easy through the use of <a href="">CSS media queries</a>, which have been supported in all major web browsers for some time now.</p>
  688. <p>Web standards and browsers have obviously not stopped evolving, which brings me to my key takeaway from this conference: the continuous evolution of browser technology is pushing the envelope of what responsive design means. We are starting to have the tools to be able to show users the information or content they desire <em>in the appropriate context</em>, and a user&rsquo;s particular device is only one of many aspects of their context (see my notes from Derek Featherstone&rsquo;s talk for examples.)</p>
  689. <p>As always, technology itself doesn&rsquo;t automatically lead to good design, but gives us the means to achieve it. Newer and better technology, when leveraged correctly, can lead to better design.</p>
  690. <p>Of course, An Event Apart Boston&rsquo;s traditional, renowned bacon cupcakes also help.</p>
  691. ]]>
  692.    </content>
  693.  </entry><entry>
  694.    <title>Send Browser Tabs from iOS to Mac with Workflow, Hazel and Dropbox</title>
  695.    <link rel="alternate" type="text/html" href="" />
  696.    <id>,2015:/2015/01/18/send_browser_tabs_from_ios_to_mac_with_workflow_hazel_and_dropbox.html</id>
  697.    <published>2015-01-18T00:00:00-05:00</published>
  698.    <updated>2015-01-18T00:00:00-05:00</updated>
  699.    <author>
  700.      <name>Josh Dick</name>
  701.      <uri></uri>
  702.    </author>
  703.    <content type="html" xml:lang="en">
  704.        <![CDATA[<blockquote>A somewhat complex solution to a simple problem.</blockquote><h2 id="introduction">Introduction</h2>
  705. <p>I&rsquo;ve always wanted to be able to send a tab from an iOS web browser to a Mac web browser. Despite the existence of browser features like Safari&rsquo;s <a href="">iCloud Tabs</a> and Google Chrome&rsquo;s <a href="">Tab Syncing</a>, or even services like <a href="">Instapaper</a> or <a href="">Pocket</a>, I wanted a way to &ldquo;send and forget&rdquo; a browser tab from an iOS device to a Mac for future reference, then close the tab on my iOS device without giving it another thought.</p>
  706. <p>When <a href="">Workflow</a> for iOS launched in December 2014, I knew that I could use it to implement this idea.</p>
  707. <p>The system described below should work with any iOS browser that uses the standard iOS share sheet, as well as any Mac browser on the receiving end. I&rsquo;ve tested this system with different combinations of Chrome and Safari on both sides, and it works great in all cases.</p>
  708. <p>I will not go into step-by-step detail for configuring <a href="">Workflow</a> or <a href="">Hazel</a>, so if you&rsquo;re new to either of them, you should download them and experiment with them before continuing.</p>
  709. <h2 id="how-it-works">How It Works</h2>
  710. <p>This is how the system works from end to end, which should give you some context before you start configuring things:</p>
  711. <ul>
  712. <li>On iOS, a Workflow Action Extension that accepts URLs is invoked through the browser&rsquo;s share sheet.</li>
  713. <li>The workflow prompts for a Mac to send the tab to, and then saves the URL in a text file, located in a Dropbox folder corresponding to the chosen Mac.</li>
  714. <li>A Hazel rule on the chosen Mac continuously monitors that same Dropbox folder for changes.</li>
  715. <li>If a new file is detected in the folder, the rule reads its contents (the URL), and opens that URL in your Mac browser of choice.</li>
  716. <li>The rule then deletes the file since it is no longer needed.</li>
  717. </ul>
  718. <h2 id="prerequisites">Prerequisites</h2>
  719. <ul>
  720. <li><a href="">Workflow</a> must be installed on all iOS devices you want to send tabs from.</li>
  721. <li><a href="">Dropbox</a> and <a href="">Hazel</a> must be installed on all Macs that will receive sent tabs.</li>
  722. </ul>
  723. <h2 id="configure-dropbox">Configure Dropbox</h2>
  724. <p>Make a list of all Macs you want to be able to send tabs to. My Macs are named after characters from the television show <a href="">Archer</a>, so my list looks like this:</p>
  725. <ul>
  726. <li>archer</li>
  727. <li>cheryl</li>
  728. <li>malory</li>
  729. </ul>
  730. <p>If you aren&rsquo;t weird enough to name your computers, your list might include things like &ldquo;MacBook Pro&rdquo; and &ldquo;iMac&rdquo;.</p>
  731. <p>Create a new folder anywhere in your Dropbox called &ldquo;Send Tab&rdquo; or anything else that works for you, and then create subfolders inside it for each Mac on your list.</p>
  732. <p>My directory structure looks like this:</p>
  733. <pre><code>$ tree ~/Dropbox/App\ Databases/Workflow/Send\ Tab
  734. /Users/Josh/Dropbox/App Databases/Workflow/Send Tab
  735. ├── archer
  736. ├── cheryl
  737. └── malory
  739. 3 directories, 0 files
  740. </code></pre>
  741. <h2 id="configure-hazel-on-your-macs">Configure Hazel on your Macs</h2>
  742. <p>The Hazel rule shown below should be configured for each Mac on your list.</p>
  743. <p>On each Mac, the rule should be configured to monitor the corresponding Dropbox subfolder that you created for that Mac.</p>
  744. <p>You can change <code>&quot;Google Chrome&quot;</code> to any browser you want, and you can opt to use different browsers on different Macs if you wish. Make sure that the browser you choose is inside your Mac&rsquo;s <code>/Applications</code> folder, that you type the browser&rsquo;s name exactly as it appears there, and that the browser&rsquo;s name is quoted, as shown.</p>
  745. <p><img src="/post_assets/2015/01/hazel_rule.png" alt="Hazel rule configuration"></p>
  746. <p>For your copying-and-pasting convenience, here&rsquo;s the script that is embedded in the Hazel rule:</p>
  747. <pre><code>url=`cat &quot;$1&quot;`
  748. open -a &quot;Google; &quot;$url&quot;
  749. rm -f &quot;$1&quot;
  750. </code></pre>
  751. <h2 id="configure-workflow-on-your-ios-devices">Configure Workflow on your iOS Devices</h2>
  752. <p>The Workflow workflow (not a typo!) shown below should be configured on each iOS device you want to send tabs from.</p>
  753. <p>This workflow is an Action Extension workflow that is configured to accept URLs.</p>
  754. <p><strong>For convenience, you can <a href="">install the workflow by visiting this link on your iOS device</a> instead of reconstructing it manually.</strong></p>
  755. <p>If you&rsquo;re curious, here&rsquo;s what the workflow looks like:</p>
  756. <p><img src="/post_assets/2015/01/workflow.png" alt="Hazel rule configuration"></p>
  757. <p>You&rsquo;ll need to customize the list of Macs, as well as the &ldquo;Destination Path&rdquo; in the &ldquo;Save to Dropbox&rdquo; action.</p>
  758. <p>A key point is that the Destination Path ends with a variable that corresponds to the selected Mac. For reference, my Destination Path looks like this, although it doesn&rsquo;t all fit on the screen in the Workflow app: <code>App Databases/Workflow/Send Tab/&lt;computer&gt;</code>. <strong>This means that the Macs in the workflow&rsquo;s list need to match their corresponding subfolder names in Dropbox.</strong></p>
  759. <h2 id="the-finish-line">The Finish Line</h2>
  760. <p>Now that you&rsquo;ve finished configuring Hazel and Workflow, you should be able to send browser tabs from your iOS device(s) to your Mac(s), like this:</p>
  761. <!-- raw HTML omitted -->
  762. <h2 id="closing-thoughts">Closing Thoughts</h2>
  763. <p>As of this writing, Hazel and Dropbox <a href=";t=4044">don&rsquo;t always work together on OS X Yosemite</a>. If Workflow is adding files to your Dropbox but the Hazel rule never triggers on its own/only works when run manually, try this workaround I that discovered through experimentation: Create a folder somewhere outside Dropbox on your Mac, configure the Hazel rule to watch it. Then, symlink that folder into your Dropbox folder, in a location that it will appear as that Mac&rsquo;s &ldquo;send tab&rdquo; subfolder (to match the iOS workflow.)</p>
  764. <p>Here&rsquo;s an example of how to set up the workaround:</p>
  765. <pre><code>$ ln -s ~/path/to/the/real/folder/cheryl ~/Dropbox/App\ Databases/Workflow/Send\ Tab/cheryl
  766. </code></pre>
  767. <p>Allowing Hazel to watch the non-Dropbox folder allows Hazel&rsquo;s automatic rule triggering to work, while still allowing Dropbox syncing to work via the symbolic link.</p>
  768. <p>If you&rsquo;re obsessed with sending tabs between devices like me, you might enjoy these two relevant free utilities:</p>
  769. <ul>
  770. <li><a href="">CloudyTabs</a>, which is a Mac menu bar application that simply lists iCloud tabs across all devices. It&rsquo;s useful if you like using Safari on your iOS devices and a different browser on the Mac.</li>
  771. <li><a href="">Chrome2ChromeV2</a>, which allows you to send tabs between Google Chrome sessions on any computer, as long as you&rsquo;ve signed into Chrome with a Google account on the desired computers.</li>
  772. </ul>
  773. <p><em><strong>Updated on January 28, 2015:</strong> Updated the Hazel rule embedded script and associated screenshot to use and be compatible with bash — which is the default for most users — instead of zsh.</em></p>
  774. ]]>
  775.    </content>
  776.  </entry><entry>
  777.    <title>An Event Apart Boston 2014</title>
  778.    <link rel="alternate" type="text/html" href="" />
  779.    <id>,2014:/2014/05/02/an_event_apart_boston_2014.html</id>
  780.    <published>2014-05-02T00:00:00-05:00</published>
  781.    <updated>2014-05-02T00:00:00-05:00</updated>
  782.    <author>
  783.      <name>Josh Dick</name>
  784.      <uri></uri>
  785.    </author>
  786.    <content type="html" xml:lang="en">
  787.        <![CDATA[<blockquote>My notes from An Event Apart, &ldquo;the design conference for people who make websites&rdquo;.</blockquote><p><img src="/post_assets/2014/05/aea_boston_2014_swag.jpg" alt="An Event Apart SWAG"></p>
  788. <h1 id="introduction">Introduction</h1>
  789. <p>I had the privilege to once again attend An Event Apart, &ldquo;the design conference for people who make websites.&rdquo; My notes from <a href="">An Event Apart Boston 2014</a> follow this introduction. The notes are grouped by talk, in the order that each talk happened at the conference.</p>
  790. <p>During his talk at the conference, <a href="">Scott Berkun</a> mentioned his concept of <a href="">Min/Max Note Taking</a>. This got me thinking about my approach to conference note taking (and publishing). During the conference, I try to capture as many interesting or useful points in my notes as I can, in real time. This method of note taking certainly doesn&rsquo;t work for everyone, but I find that it helps reinforce the speakers&rsquo; ideas in my head.</p>
  791. <p>Notes in summary or &ldquo;handful of bullets&rdquo; format would certainly be easier to consume than the wall of text that appears below, but the notion of trying to summarize others&rsquo; ideas for consumption doesn&rsquo;t sit right with me. Summarizing could filter out information or ideas that someone could find useful, or even worse, could accidentally skew the information. To that end, I decided stick with the &ldquo;wall of text&rdquo; approach to publishing my notes that I&rsquo;ve <a href="/2012/08/19/an_event_apart_boston_2012.html">used</a>. Before publishing my notes here, I extensively edit them for clarity and typos, but I don&rsquo;t make any attempt to summarize them or make them otherwise more digestible.</p>
  792. <p>If you&rsquo;re interested, my notes from An Event Apart Boston <a href="/2012/08/19/an_event_apart_boston_2012.html">2013</a> are also available.</p>
  793. <h1 id="day-1-42814">Day 1: 4/28/14</h1>
  794. <h2 id="jeffrey-zeldman---understanding-web-design-zeldmancomhttpwwwzeldmancom-bull-zeldmanhttpstwittercomzeldman">Jeffrey Zeldman - Understanding Web Design (<a href=""></a> • <a href="">@zeldman</a>)</h2>
  795. <ul>
  796. <li><strong>The mystery of web design:</strong> Those that can&rsquo;t value your work can&rsquo;t support you in creating your best work.</li>
  797. <li>Nobody outside our industry knows what we do; it&rsquo;s hard to explain in non-technical terms.</li>
  798. <li>In a team setting, it&rsquo;s hard enough to achieve great design even when a team is familiar with design.</li>
  799. <li>Understanding a client&rsquo;s business can be more important to a client than your technical expertise.</li>
  800. <li>Doing a personal project helps you break out of the work you&rsquo;re doing at your job, and if it&rsquo;s public, helps make people aware of you.</li>
  801. <li>Outside the industry, are there any well-known organizations that advocate for good design?
  802. <ul>
  803. <li>The <a href="">Webby Awards</a> are good at getting media attention and putting on a great show, but don&rsquo;t necessarily for exhibit good web or interaction design. They get the old media to pay attention to the Internet.</li>
  804. <li>The <a href="">net Awards</a> actually judge design merits, but your boss and client won&rsquo;t know about them.</li>
  805. <li>&ldquo;Nobody understands the W3C besides the W3C.&rdquo; The W3C speaks for themselves, not us.</li>
  806. <li>Companies speak to us but not for us; Apple wants you to love your iPhone, not HTML.</li>
  807. </ul>
  808. </li>
  809. <li>Regarding Facebook&rsquo;s HTML5 vs native app debacle, Facebook approached mobile as a <strong>technology</strong> problem, when it was really a <strong>design</strong> problem. Anything extraneous to Facebook&rsquo;s core functionality (e.g. sharing pictures with friends) doesn&rsquo;t belong in Facebook on mobile <em>or</em> on the desktop.</li>
  810. <li>HTML5 vs. native is the wrong question. Instead of emulating the desktop experience on mobile, replicate what users love about the experience.</li>
  811. <li>Companies harvest data to serve their advertisers instead of their customers.</li>
  812. <li>You&rsquo;re paid to meet business goals, not to make elegant technical achievements that shouldn&rsquo;t have been attempted in the first place.</li>
  813. <li>Web design isn&rsquo;t about technology. It&rsquo;s about people.
  814. <ul>
  815. <li>We don&rsquo;t design for browsers; we design for people to ensure that they have a good experience.</li>
  816. <li>We don&rsquo;t use progressive enhancement or make a page accessible for gold stars; we design experiences for people.</li>
  817. </ul>
  818. </li>
  819. <li>To criticize something you don&rsquo;t understand because it doesn&rsquo;t behave as something you do understand is wrong (for example: &ldquo;Web design is shoddy because it hasn&rsquo;t produced a work as influential as Milton Glaser&rsquo;s Bob Dylan poster.&quot;) There&rsquo;s no Mona Lisa of television.</li>
  820. <li>Web design is not book design, it is not poster design, it is not illustration, and the highest achievements of those disciplines are not what web design aims for.</li>
  821. <li>Web design is like architecture or type design. After an architect&rsquo;s design is done, they relinquish control to the builders and the people who use the building.</li>
  822. <li>Web design is the creation of digital environments that facilitate and encourage human activity; reflect or adapt to individual voices and content; and change gracefully over time while always retaining their identity.</li>
  823. <li>Great web design:
  824. <ul>
  825. <li>makes interaction easy.</li>
  826. <li>guides you subtly to your heart&rsquo;s desire; design is never passive, even if it looks that way.</li>
  827. <li>can be invisible or in your face.</li>
  828. <li>delights.</li>
  829. <li>is not innovative for the sake of innovation.</li>
  830. </ul>
  831. </li>
  832. <li>At work:
  833. <ul>
  834. <li>Represent your profession.</li>
  835. <li>Don&rsquo;t wait to be asked to do your job.</li>
  836. <li>Arrive early and often.</li>
  837. <li>Push your way in. <em>Volunteer.</em></li>
  838. <li>Achieve the right things for the wrong reasons. (For example, The Cold War led to the space race and the moon landing.)</li>
  839. <li>Your boss will never care about the web for the same reasons you do. Your job is to find the reasons they&rsquo;ll care about.</li>
  840. </ul>
  841. </li>
  842. <li>We are all evangelists; we need evangelists more than we need superstars.</li>
  843. </ul>
  844. <hr>
  845. <h2 id="sarah-parmenter---designing-using-data-sazzycoukhttpwwwsazzycouk-bull-sazzyhttpstwittercomsazzy">Sarah Parmenter - Designing Using Data (<a href=""></a> • <a href="">@sazzy</a>)</h2>
  846. <ul>
  847. <li>&ldquo;Design is no longer the killer differentiator.&rdquo; -John Maeda</li>
  848. <li>Instincts are experiments. Data is proof.</li>
  849. <li>&ldquo;&hellip;become an expert to facilitate the most productive conversation you can have.&rdquo; -Kevin Hoffman, An Event Apart 2014</li>
  850. <li>&ldquo;Many designers who are skilled technicians, craftsmen, or researchers have struggled to survive in the messy environment required to solve today&rsquo;s complex problems. They may play a valuable role, but they are destined to live in the downstream world of design execution.&rdquo; -Tim Brown, IDEO</li>
  851. <li>Compared to learning a new tool, designing using data has a much bigger impact over a much shorter time.</li>
  852. <li>Being able to design with data is what will keep us valuable.</li>
  853. <li>It&rsquo;s easy to think of data/content as not part of our job.</li>
  854. <li>&ldquo;Research is formalized curiosity. It is poking and prodding with a purpose.&rdquo; -Zora Neale Hurston</li>
  855. <li>&ldquo;No one has an excuse to make an uninformed decision anymore.&rdquo; -Federico Holgado, Mailchimp</li>
  856. <li>&ldquo;Being a good designer is no longer enough. We need designers that can tell you WHY they design something a certain way.&rdquo;</li>
  857. <li>&ldquo;&hellip;designers go from decorators to problem solvers.&rdquo; -Aaron Walter, Mailchimp</li>
  858. <li>&ldquo;(If) a strategy can&rsquo;t predict outcomes, our strategy is broken.&rdquo; -Jared Spool, An Event Apart 2014</li>
  859. <li><strong>Vanity metrics</strong> are pieces of data on which you cannot act and exist purely for ego-stroking:
  860. <ul>
  861. <li>hits</li>
  862. <li>total signups</li>
  863. <li>page views</li>
  864. <li>number of visits</li>
  865. <li>unique visitors</li>
  866. <li>likes</li>
  867. </ul>
  868. </li>
  869. <li>A metric needs to tell you something tangible to act on.</li>
  870. <li>&ldquo;Making your numbers go up (any numbers&ndash;your BMI, your blood sugar, your customer service ratings) is pointless if the numbers aren&rsquo;t related to why you went to work this morning.&rdquo; -Seth Godin</li>
  871. <li>Track people and their habits.</li>
  872. <li>These are tools that can be used responsibly to do just that: <a href="">Minimaltyics</a>, <a href="">KISSmetrics</a>, <a href="">GoSquared</a>, <a href=""></a>, <a href="">Mixpanel</a>, <a href="">Chartbeat</a>, <a href="">TrueSocialMetrics</a>, <a href="">crazyegg</a></li>
  873. <li><a href="">BrowserStack</a> for cross-browser testing</li>
  874. <li><a href="">Optimizely</a> for A/B testing</li>
  875. <li>Seth Godin&rsquo;s &ldquo;purple cow&rdquo; business is a business that does something that bucks the trend of what a related business would be.</li>
  876. <li>&ldquo;Experiment led design may happen outside of normal work.&rdquo; -Kevin Hoffman</li>
  877. <li>People like honesty; they see through sales patter. Don&rsquo;t be afraid to share your failures.</li>
  878. <li>Referrer loyalty: Those who arrive at your site from a referrer are likely to arrive at your site from the same referrer in the future.</li>
  879. <li><a href="">Blushbar</a>:
  880. <ul>
  881. <li>Used social metrics to optimize social reach.</li>
  882. <li>Realized they needed an iPhone app because people didn&rsquo;t know how to bookmark the appointment booking web page.</li>
  883. <li>It&rsquo;s the small things that make you stand out from the crowd. (For example, Blushbar gave out umbrellas in case of rain.)</li>
  884. <li>Changing &ldquo;book appointment&rdquo; to &ldquo;book YOUR appointment&rdquo; resulted in a 200% increase.</li>
  885. </ul>
  886. </li>
  887. <li>For <a href="">Highrise</a>, &ldquo;see plans and pricing&rdquo; was a more effective web call to action than &ldquo;start your 30-day free trial&rdquo;.</li>
  888. <li>Good visual media creates a more positive perception of the value of the product or service you&rsquo;re selling.
  889. <ul>
  890. <li>But, content comes first!</li>
  891. <li>Use &ldquo;real-world&rdquo; imagery instead of professionally created imagery; too much polish can look like stock imagery. (Made the difference between 0 clicks vs 521 clicks in two Facebook campaigns with the exact same title and wording.)</li>
  892. </ul>
  893. </li>
  894. <li>Web-savvy people have a higher tolerance for bad design.</li>
  895. <li>If you can&rsquo;t communicate your findings in the words of your boss/clients, you&rsquo;ve failed to help them find value from those findings.</li>
  896. <li>&ldquo;A mind is like a parachute. It doesn&rsquo;t work if it is not open.&rdquo; -Frank Zappa</li>
  897. </ul>
  898. <p>I should point out that Sarah&rsquo;s &ldquo;Designing with Data&rdquo; presentation used data from her business, <a href="">Blushbar</a>, to make its points. <a href="">I was impressed</a> that she used the presentation itself to practice what she preached.</p>
  899. <hr>
  900. <h2 id="dan-mall---responsive-design-is-still-hardeasy-be-afraiddont-worry-danielmallcomhttpdanielmallcom-bull-danielmallhttpstwittercomdanielmall">Dan Mall - Responsive Design is Still Hard/Easy! Be Afraid/Don&rsquo;t Worry! (<a href=""></a> • <a href="">@danielmall</a>)</h2>
  901. <p>Dan outlined a &ldquo;modern web design process, in four easy payments.&rdquo;</p>
  902. <ol>
  903. <li>Plan (research and hypothesize)</li>
  904. <li>Inventory
  905. <ul>
  906. <li><strong>Content inventory:</strong> A simple content strategy for <del>dummies</del> designers is to add/edit/remove components as necessary to fit the content.</li>
  907. <li><strong>Performance inventory:</strong> Calculate your performance budget before designing, since it can help focus your design (number of images, JS libraries, etc.)</li>
  908. <li><strong>Pattern inventory:</strong>
  909. <ul>
  910. <li>Atoms (HTML tags)</li>
  911. <li>Molecules (collections of atoms, for example &ldquo;Image with Caption&rdquo;)</li>
  912. <li>Organisms (collections of molecules, for example &ldquo;Article Body&rdquo; or &ldquo;Carousel&rdquo;)</li>
  913. <li>See <a href=""></a> for an example of a pattern inventory.</li>
  914. </ul>
  915. </li>
  916. <li><strong>Visual inventory:</strong>
  917. <ul>
  918. <li>If you want to get a better understanding of something, asking a question is infinitely more useful than making a statement.&rdquo; -Jason Santa Maria, <a href="">The Pastry Box</a></li>
  919. <li>&ldquo;Is showing their app on a laptop on the homepage the best way to sell it to prospective customers?&rdquo;</li>
  920. <li>&ldquo;Can their brand pull off a minimalist design approach?&rdquo;</li>
  921. <li>&ldquo;Should their copy be more playful?&rdquo; Would a playful design with kitschy illustrations make you grin as you explore the site?</li>
  922. <li>Rather than wasting time creating comps, splice the customer&rsquo;s logo into an existing design. This allows the customer to see themselves in a certain light without putting lots of effort into comps. Would a design for CNN be appropriate if its logo was simply spliced into a different, existing site?</li>
  923. </ul>
  924. </li>
  925. </ul>
  926. </li>
  927. <li>Sketch — explore ideas roughly and quickly.
  928. <ul>
  929. <li><a href="">Content reference wireframes</a></li>
  930. <li><strong>Linear design:</strong> List out all of the components of the page (header, grids, footer, etc.) and just block them out as gray boxes. This allows you to see which components should have more space devoted to them relative to other components.</li>
  931. <li>It&rsquo;s easy to make boxes responsive but harder to make a web site cohesively responsive.</li>
  932. <li><strong>Element collages:</strong> Turn powerful phrases into visual hooks.
  933. <ul>
  934. <li>&ldquo;Obviously this isn&rsquo;t a website, but I see how it could be one.&rdquo; -The perfect client&rsquo;s reaction to an element collage</li>
  935. <li>Make an element collage horizontal so a client doesn&rsquo;t mistake it for a web site comp.</li>
  936. <li>&ldquo;Element collages are like giving your client a peek at all those hidden layers.&rdquo; -Paul Lloyd</li>
  937. </ul>
  938. </li>
  939. <li>Prototyping, with problem and solution statements: &ldquo;This prototype does one thing and one thing only.&rdquo; The first prototype should be something any developer can do; prototypes should get iteratively more complex and fleshed out.</li>
  940. </ul>
  941. </li>
  942. <li>Assemble
  943. <ul>
  944. <li>&ldquo;Assembling the site should take the least time on the project. The real work is research, sketching, prototyping.&rdquo;</li>
  945. <li>Responsive web design should act as a catalyst for:
  946. <ul>
  947. <li>Availability of content</li>
  948. <li>Performance</li>
  949. <li>Accessibility</li>
  950. <li>Organizational change</li>
  951. <li>Progressive enhancement</li>
  952. <li>Workflow</li>
  953. <li>Business benefits</li>
  954. </ul>
  955. </li>
  956. </ul>
  957. </li>
  958. </ol>
  959. <hr>
  960. <h2 id="luke-wroblewski---screen-time-lukewcomhttpwwwlukewcom-bull-lukewhttpstwittercomlukew">Luke Wroblewski - Screen Time (<a href=""></a> • <a href="">@lukew</a>)</h2>
  961. <h3 id="know-your-screen">Know Your Screen</h3>
  962. <ul>
  963. <li>In 2013, enough LCD screens were sold to dedicate 0.5 square feet of LCD to every human on earth.</li>
  964. <li>In a world of glass, online time is screen time.</li>
  965. </ul>
  966. <h3 id="output">Output</h3>
  967. <ul>
  968. <li>When creating web content, use:
  969. <ul>
  970. <li>Image resources represented as vectors rather than as raster pixels whenever possible.</li>
  971. <li>CSS and web type whenever possible.</li>
  972. <li>SVG and icon fonts whenever applicable.</li>
  973. <li><a href="">Picturefill</a> (for now) if you need to use raster graphics.</li>
  974. </ul>
  975. </li>
  976. <li>Increase font sizes on screens that are wide enough but not tall enough <a href="">for it to make sense</a>.</li>
  977. <li>For widescreen layouts:
  978. <ul>
  979. <li>Tighten up the layout by vertically compressing whitespace.</li>
  980. <li>Move calls to action closer to the top.</li>
  981. </ul>
  982. </li>
  983. <li>For portrait layouts:
  984. <ul>
  985. <li>Rebalance widescreen layouts by minimizing menus and maximizing content.</li>
  986. <li>Menus can be repositioned off-canvas or at a different portion of the screen (even the bottom; repositioning towards the bottom works better than to the sides.)</li>
  987. </ul>
  988. </li>
  989. <li>Output trends:
  990. <ul>
  991. <li>High resolution is <strong>the</strong> resolution.</li>
  992. <li>Widescreen is <strong>the</strong> aspect ratio (16:9 or even 19:10).</li>
  993. <li>Media queries know about more than width alone; pay attention to variable heights as well!</li>
  994. </ul>
  995. </li>
  996. </ul>
  997. <h3 id="input">Input</h3>
  998. <ul>
  999. <li>Not all devices correctly report whether they are touch capable, so support <strong>all</strong> inputs (<strong>both</strong> touch and click-based input.)</li>
  1000. <li>You can include &ldquo;hidden features&rdquo; for each set of inputs. For example, double tapping an image in a touch interface and mouse-wheel scrolling in a click interface could both perform the same &ldquo;zoom&rdquo; action.</li>
  1001. <li>Communicate what&rsquo;s possible.</li>
  1002. <li>Screen size is a poor proxy for detecting input type, but it&rsquo;s what we&rsquo;ve got&hellip;for now.</li>
  1003. </ul>
  1004. <h3 id="posture">Posture</h3>
  1005. <ul>
  1006. <li><strong>Posture</strong> is how we combine input and output.</li>
  1007. <li>Physical screen size and viewing distance determine the final perceived size of objects (in real-world units like inches, not in pixels!)</li>
  1008. <li>Objects should be sized approximately 1/2 inch per foot of viewing distance. (Example: the box art in all of Netflix&rsquo;s UIs across different devices of increasing size.)</li>
  1009. <li>A full HD resolution TV can have the same resolution as a phone (1920px × 1080px), even though one is viewed ten feet away while the other is viewed one foot away.</li>
  1010. <li>Design to human scale and environments, not to screen width.</li>
  1011. </ul>
  1012. <hr>
  1013. <h2 id="kristina-halvorson---contentcommunication-braintrafficcomhttpbraintrafficcom-bull-halvorsonhttpstwittercomhalvorson">Kristina Halvorson - Content/Communication (<a href=""></a> • <a href="">@halvorson</a>)</h2>
  1014. <h3 id="principles">Principles</h3>
  1015. <p>A <strong>principle</strong> internally motivates us to do things that seem good and right.
  1016. A <strong>rule</strong> externally compels you to do things <em>someone else has deemed</em> good and right.</p>
  1017. <h3 id="content-principles">Content Principles</h3>
  1018. <ul>
  1019. <li>Principles unite us in our day-to-day-work.</li>
  1020. <li>This content is not for us.</li>
  1021. <li>&ldquo;Responsive&rdquo; does not equal &ldquo;reactive&rdquo;.</li>
  1022. <li>The story informs the format.</li>
  1023. <li>Numbers aren&rsquo;t everything.</li>
  1024. </ul>
  1025. <h3 id="strategy">Strategy</h3>
  1026. <ul>
  1027. <li>A good strategy provides you with context and constraints, and doesn&rsquo;t allow you do do anything/make excuses for anything: &ldquo;We will share user-facing, task-based content that makes our customers feel smart and safe, both personally and professionally.&rdquo;</li>
  1028. <li>Strategy keeps us accountable.</li>
  1029. <li>Strategy helps web teams ask better questions about content at the beginning of a project.</li>
  1030. <li>A <strong>content strategy</strong> consists of <strong>content components</strong> (substance and structure) and <strong>people components</strong> (workflow and governance).</li>
  1031. </ul>
  1032. <h3 id="process">Process</h3>
  1033. <ul>
  1034. <li>Do not make process your god.</li>
  1035. <li>&ldquo;Different methods work or fail because of people, not because they are universally good or bad.&rdquo; -Pawel Brodzinski, <em>Agile Bullshit</em></li>
  1036. <li>Artifacts (fonts, etc) are tools, not outcomes.</li>
  1037. <li>Good process helps us move together.</li>
  1038. </ul>
  1039. <h3 id="roles">Roles</h3>
  1040. <ul>
  1041. <li>Roles give us a place.</li>
  1042. <li>The RACI Model:
  1043. <ul>
  1044. <li><strong>R</strong> - Who is <strong>responsible</strong> for completing a task?</li>
  1045. <li><strong>A</strong> - Who is <strong>accountable</strong> for the work&rsquo;s success?</li>
  1046. <li><strong>C</strong> - Who must be <strong>consulted</strong> before work can be signed-off on?</li>
  1047. <li><strong>I</strong> - Who must be kept <strong>informed</strong> along the way?</li>
  1048. </ul>
  1049. </li>
  1050. <li>For every project, every time:
  1051. <ol>
  1052. <li>At some point, invite All the People</li>
  1053. <li>Make sure everyone&rsquo;s aligned on terminology (e.g. <em>audit</em> vs. <em>inventory</em>, <em>wireframe</em> vs. <em>prototype</em>)</li>
  1054. <li>Identify timing issues, agendas, overlapping responsibilities</li>
  1055. </ol>
  1056. </li>
  1057. </ul>
  1058. <h3 id="perceptions">Perceptions</h3>
  1059. <ul>
  1060. <li>Perceptions give way to perspective.</li>
  1061. <li>&ldquo;In content strategy, our master skills must include translating and negotiating, so we can facilitate communication between disparate disciplines and help them to communicate.&rdquo; -Rachel Lovinger, <em>Tinker, Tailor, Content Strategist</em></li>
  1062. </ul>
  1063. <h3 id="conclusion">Conclusion</h3>
  1064. <ul>
  1065. <li>We are perpetually catching up.</li>
  1066. <li>Our work is <del>personal</del> <em>together</em>.</li>
  1067. <li>&ldquo;This multi-device web design increases stress exponentially.&rdquo; -Trent Walton, <em>.net Magazine</em></li>
  1068. <li>&ldquo;A study of over 350 people in 6 business units at a financial services company found that the greatest predictor of a team&rsquo;s achievement was how the members felt about one another.&rdquo; -Shawn Achor, <em>The Happiness Advantage</em></li>
  1069. </ul>
  1070. <hr>
  1071. <h2 id="jared-spool---ux-strategy-means-business-uiecomhttpwwwuiecom-bull-jaredspoolhttpstwittercomjaredspool">Jared Spool - UX Strategy Means Business (<a href=""></a> • <a href="">@jaredspool</a>)</h2>
  1072. <h3 id="design-and-business">Design and Business</h3>
  1073. <ul>
  1074. <li>Design is the rendering of intent.</li>
  1075. <li>Every design has content, and every design has&hellip; &hellip;a design.</li>
  1076. <li>Great content and great design both exist, but we tend to treat them as separate entities. We believe they overlap with great UX, but in truth they are inseparable: great content + great design = great UX.</li>
  1077. <li>We use <em>strategy</em> to achieve a desired outcome, but UX strategy can&rsquo;t predict outcomes.</li>
  1078. <li>Regarding Apple&rsquo;s iOS 6 Maps fiasco: Apple acquired 3 mapping companies and used 10 data sources; Google used 1,300 data sources and had 1,000 people × 10 years of correcting map errors. Apple didn&rsquo;t do the wrong things, Google had done it better 10 years earlier. We were comparing 10-year-old vs. 1-year-old process and strategy.</li>
  1079. <li>Amazon&rsquo;s cash float model:
  1080. <ul>
  1081. <li>Amazon doesn&rsquo;t focus on profit for most of the things they sell, because they can sell everything at cost and still make money.</li>
  1082. <li>Amazon turns inventory every 20 days while Best Buy turns inventory every 74 days.</li>
  1083. <li>Standard retail payment terms are 45 days.</li>
  1084. <li>Best Buy has a cash debt before distributors are paid; Amazon has a cash float.</li>
  1085. </ul>
  1086. </li>
  1087. <li>Great business models are explicitly designed.</li>
  1088. <li>How business is done in Silicon Valley: <a href="">South Park&rsquo;s &ldquo;Underpants Gnomes&rdquo; model</a> (1. Steal underpants; 2. ???; 3. Profit)</li>
  1089. <li>Business strategic priorities:
  1090. <ul>
  1091. <li>Increase revenue</li>
  1092. <li>Decrease costs</li>
  1093. <li>Increase new business</li>
  1094. <li>Increase existing business</li>
  1095. <li>Increase shareholder value</li>
  1096. </ul>
  1097. </li>
  1098. <li>Can apply those strategic priorities to any business (examples: Zappos&rsquo; pioneering self-return policy, universities, government, etc.)</li>
  1099. <li>Framing work in these terms helps communicate it to the people who are responsible for the health of the organization.</li>
  1100. </ul>
  1101. <h3 id="types-of-business-models">Types of Business Models</h3>
  1102. <ul>
  1103. <li><strong>Advertising</strong> is a business model failure (For example: look at how <a href="">cluttered is</a>.)
  1104. <ul>
  1105. <li>Everything that isn&rsquo;t content on a page is there to disrupt the user from the experience they intended to have.</li>
  1106. <li>It&rsquo;s intentional and it disrupts the user.</li>
  1107. <li>Advertisers don&rsquo;t care about the user; they care about selling stuff.</li>
  1108. <li>Advertising disrupt&rsquo;s the users&rsquo; experience supposedly to benefit the advertiser.</li>
  1109. <li>Internet advertising statistics:
  1110. <ul>
  1111. <li>A typical internet user sees 1,707 ads in a year. (Comscore)</li>
  1112. <li>An average ad is clicked 0.1% of the times it is shown. (Doubleclick)</li>
  1113. <li>A 468px × 60px banner is clicked 0.04% of the times it is shown. (Doubleclick)</li>
  1114. <li>Users can&rsquo;t see 31% of ads. (Comscore)</li>
  1115. <li>Users click on 50% of mobile ads by accident. (Goldspot Media)</li>
  1116. <li>You are 475.29 times more likely to survive a plane crash than to click on a banner ad in your lifetime. (Solve Media)</li>
  1117. </ul>
  1118. </li>
  1119. <li>Regarding <a href="">K-Mart&rsquo;s &ldquo;ship my pants&rdquo; ad</a>: &ldquo;I&rsquo;ve watched this ad a thousand times. I love this ad; I will never shop at K-Mart.&rdquo;</li>
  1120. <li>When you don&rsquo;t <em>pay</em> for the product, you <em>are</em> the product.</li>
  1121. <li><a href=""></a>: 3.8% of the screen real estate is dedicated to the top 5 most accessed elements on the page, which account for 60% of traffic. The rest of the page is crammed with marketing stuff users don&rsquo;t care about.</li>
  1122. <li>Internet advertising that could actually work relies on <em>seducible moments</em>, when an ad  delivers the right content at the right time.</li>
  1123. <li>Figuring out what products go with what content is prohibitively difficult and expensive, but it works because it is purposely built into the experience.</li>
  1124. <li>Advertising should be the business model choice of last resort.</li>
  1125. </ul>
  1126. </li>
  1127. <li>Metered paywalls
  1128. <ul>
  1129. <li><a href=""></a>: Only users who return to the site multiple times are shown the paywall (limited to 10 articles for free.)</li>
  1130. <li>NY Times made more money from the metered paywall than from advertising. This plays into the business strategic priorities.</li>
  1131. <li>Metered paywalls demand excellent content.</li>
  1132. </ul>
  1133. </li>
  1134. <li>Supporting product sales
  1135. <ul>
  1136. <li><a href="">iFixit</a> shares information about repairing electronic devices, and sells the specialized tools needed to do so.</li>
  1137. <li><a href="">Etsy</a> sells instructions to make products as well as the products themselves.</li>
  1138. </ul>
  1139. </li>
  1140. <li>Alternative Channel Revenue
  1141. <ul>
  1142. <li><a href="">Radiolab</a> makes more money from their live shows than from pledge drives.</li>
  1143. <li><a href="">Mythbusters On Tour</a> makes more money than television advertising.</li>
  1144. </ul>
  1145. </li>
  1146. <li>Content Distribution (examples: Amazon Kindle, Apple iTunes)</li>
  1147. </ul>
  1148. <h3 id="conclusion-1">Conclusion</h3>
  1149. <ul>
  1150. <li>Business model recap:
  1151. <ul>
  1152. <li>Metered paywalls</li>
  1153. <li>Repurposed content</li>
  1154. <li>Supporting product sales</li>
  1155. <li>In-app purchase</li>
  1156. <li>Alternative channel revenue</li>
  1157. <li>Content distribution</li>
  1158. <li>Advertising (but don&rsquo;t do it!)</li>
  1159. </ul>
  1160. </li>
  1161. <li>Content has actual monetary value!
  1162. <ul>
  1163. <li><a href="">SignificantObjects</a> turned thrift-store chotchkies objects of value by attaching stories to them.</li>
  1164. <li><a href="">Crutchfield</a> writes their own copy for items in their online store, while Walmart&rsquo;s site relies on generic information provided by vendors. In user testing, users spent 237% of their budget at Crutchfield, but only spent 89% of their budget at Walmart.</li>
  1165. </ul>
  1166. </li>
  1167. <li>The best UX strategists create delight by working in the intersection of business and design.</li>
  1168. <li>We can design intentional business models.</li>
  1169. <li>The 5 business strategic priorities are a tool for mapping our design intent into business objectives, and to map business objectives into design intention.</li>
  1170. <li>We need to study business models like we study technological techniques.</li>
  1171. </ul>
  1172. <hr>
  1173. <h1 id="day-2-42914">Day 2: 4/29/14</h1>
  1174. <h2 id="jeremy-keith---the-long-web-adactiocomhttpadactiocom-bull-adactiohttpstwittercomadactio">Jeremy Keith - The Long Web (<a href=""></a> • <a href="">@adactio</a>)</h2>
  1175. <ul>
  1176. <li>Mobile first? URL first. Design your URLs before you design anything that&rsquo;s going to appear on the screen.</li>
  1177. <li>URLs are the one universal syntax of the web. They should be readable, guessable, and hackable.</li>
  1178. <li>Content first, navigation second.</li>
  1179. <li>It&rsquo;s OK to use unsupported attributes/elements in HTML since browsers typically ignore things they don&rsquo;t understand and degrade gracefully.</li>
  1180. <li>The <a href=""><code>&lt;datalist&gt;</code> element</a> are the bastard love child of the <code>&lt;input&gt;</code> and <code>&lt;select&gt;</code> elements.</li>
  1181. <li>Any text in a <code>&lt;datalist&gt;</code> can also be used as a placeholder with a &ldquo;for example&rdquo; or &ldquo;e.g.&rdquo; prefix.</li>
  1182. <li><strong>Progressive enhancement</strong> doesn&rsquo;t mean designing for the lowest common denominator; rather it means <strong>starting</strong> from the lowest common denominator.
  1183. <ul>
  1184. <li>&ldquo;I like an escalator, because an escalator can never break. It can only become stairs. You&rsquo;ll never see an &lsquo;Escalator Out of Order&rsquo; sign, only &lsquo;Escalator Temporarily Stairs. Sorry for the convenience.'&rdquo; -Mitch Hedberg</li>
  1185. <li>&ldquo;Javascript is the electricity of the web.&rdquo; It should be &ldquo;subservient to the existing structure.&rdquo;</li>
  1186. <li>In other words, a site should be enhanced by JavaScript but not necessarily require it.</li>
  1187. <li>&ldquo;Until the page has finished loading, every user is a non-JavaScript user.&rdquo; -Jake Archibald</li>
  1188. <li>Progressive enhancement is more about technology failing than technology not being supported. (For example: <code>&lt;a href=&quot;javascript:void(0)&quot;&gt;Download&lt;/a&gt;</code> broke the ability to download Google Chrome when the download page&rsquo;s JavaScript stopped loading.)</li>
  1189. </ul>
  1190. </li>
  1191. <li>Don&rsquo;t rely on 3rd-party APIs for your core business since they could go away without notice.</li>
  1192. <li>Use conditional loading for any nonessential third-party content (for example, social widgets; write links in the HTML that will be shown while the page loads, then after the page is done loading, allow widgets to load and replace the links.)</li>
  1193. <li>The <a href=""><code>rel</code> attribute</a> can be used to make <a href="">prefretching</a> <strong>suggestions</strong> to the browser to optimize performance.</li>
  1194. <li>The best way to be future friendly is to be backwards compatible.</li>
  1195. </ul>
  1196. <hr>
  1197. <h2 id="paul-irish---responsive-design-performance-budget-paulirishcomhttppaulirishcom-bull-paul_irishhttpstwittercompaul_irish">Paul Irish - Responsive Design Performance Budget (<a href=""></a> • <a href="">@paul_irish</a>)</h2>
  1198. <ul>
  1199. <li>71% of people expect websites to load as fast (or faster) on their phone than on a computer.</li>
  1200. <li>The #1 thing you can do for your site for mobile devices is to make it faster.</li>
  1201. <li>Worry about speed way before worrying about reformatting sites to fit small screens. (Double-tap and pinch zooming are workarounds for desktop layouts, but there are no workarounds for a slow site.)</li>
  1202. <li><strong><a href="">Speed Index</a>:</strong> A metric that precisely measures a user&rsquo;s experienced page load time in milliseconds.</li>
  1203. <li>Total page bytes, number of requests, and bytes of JavaScript are not reliable indicators of actual page load times.</li>
  1204. <li>For <strong>fast pages</strong>, what is the <strong>right number of requests</strong> and <strong>optimal page size</strong>?</li>
  1205. <li>&ldquo;Measuring performance by the KB is like measuring effectiveness of your diet by the pound. Measuring performance by number of requests is like measuring your diet by number of things you ate - in both cases, who cares about what you actually ate, right?&rdquo; -<a href="">Ilya Grigorik</a></li>
  1206. <li>Not all <strong>requests</strong> are made equal; where are they initiated? What part of the UX do they block?</li>
  1207. <li>Not all <strong>bytes</strong> are made equal; the first 14kb are extremely important. Different <code>content-type</code>s can have different performance impact(s) for the page.</li>
  1208. <li>&ldquo;Bloat&rdquo; isn&rsquo;t a great word to describe performance issues, it can refer to transfer size, code complexity, or dead code.</li>
  1209. <li>Components of an HTTP request:
  1210. <ul>
  1211. <li>DNS lookup</li>
  1212. <li>New TCP connection (handshake roundtrip)</li>
  1213. <li>HTTP request requires minimum of one round trip to the server — <em>plus server processing time</em>.</li>
  1214. </ul>
  1215. </li>
  1216. <li>Bandwidth + Latency ≈ Performance.
  1217. <ul>
  1218. <li>Bandwidth: Amount of data transferred over the network per unit time (e.g. 5 mb/s)</li>
  1219. <li>Latency: Delay in the network to transfer a packet (e.g. round trip time)</li>
  1220. </ul>
  1221. </li>
  1222. <li>Last-mile latency (cable/DSL) is slow, and it&rsquo;s even worse for mobile (see <a href="">&ldquo;Living with Lag&rdquo;</a>).</li>
  1223. <li>Video streaming is bandwidth limited; web browsing is latency limited.</li>
  1224. <li>Optimizing transport (TCP) performance:
  1225. <ul>
  1226. <li>TCP is optimized for long-lived connections and bulk data transfers.</li>
  1227. <li>Most of the <strong>HTTP data flows consist of small, bursty data transfers</strong>, but network round trip time is the limiting factor in TCP throughput and performance in most cases.</li>
  1228. <li>Consequently, <strong>latency is the performance bottleneck for HTTP</strong> and most of the web.</li>
  1229. <li><strong>Latency</strong> defines the speed at which the page loads; <strong>mobile&rsquo;s growth</strong> means average latency is growing.</li>
  1230. <li>Latency&rsquo;s influence means <strong>optimizing for request count</strong>.</li>
  1231. </ul>
  1232. </li>
  1233. <li>Optimizing for the critical path
  1234. <ul>
  1235. <li>When a JavaScript file is referenced in the <code>&lt;head&gt;</code> of the document, the browser can&rsquo;t process the rest of the page until it has finished processing that file.</li>
  1236. <li>Eliminate render-blocking JavaScript (especially in <code>&lt;head&gt;</code>). Load all JavaScript asynchronously.</li>
  1237. <li><strong>Critical CSS:</strong> The CSS used to render the content &ldquo;above the fold&rdquo;.</li>
  1238. <li>Minimize render-blocking CSS.</li>
  1239. <li>Deliver the goods — serve critical content in the initial HTML, then progressively enhance.</li>
  1240. <li>No redirects (they just add round trip time).</li>
  1241. <li>Use gzip.</li>
  1242. </ul>
  1243. </li>
  1244. <li>Tools that can help: <a href="">WebPagetest</a> / <a href="">Google PageSpeed Insights</a> / <a href="">Pagespeed Module (apache/nginx)</a> / <a href="">speedcurve</a></li>
  1245. <li>Visualize your performance wins! Use visuals and data to make your case for improving performance.</li>
  1246. <li>Your count of high-latency users is going to increase. Prepare for it.</li>
  1247. <li>Aggressive but good performance goals:
  1248. <ul>
  1249. <li>Deliver a fast mobile web page load (show above-the-fold content in under 1 second (Speed Index under 1000). Serve critical-path content, including CSS, as part of the first 14kb of the first server response.</li>
  1250. <li>Delight your users.</li>
  1251. </ul>
  1252. </li>
  1253. </ul>
  1254. <hr>
  1255. <h2 id="lea-verou---the-chroma-zone-engineering-color-on-the-web-leaveroumehttpleaveroume-bull-leaverouhttpstwittercomleaverou">Lea Verou - The Chroma Zone: Engineering Color on the Web (<a href=""></a> • <a href="">@LeaVerou</a>)</h2>
  1256. <h3 id="screens-pixels-and-subpixels">Screens, Pixels, and Subpixels</h3>
  1257. <ul>
  1258. <li>White pixels are actually composed of RGB subpixels, using additive color.</li>
  1259. <li>Different screens have different subpixel geometries.</li>
  1260. <li>Text is rendered with subpixel antialiasing; you can play with it using <a href="">Subpixel Explorer</a>.</li>
  1261. <li>Browsers allow you to explicitly disable antialiasing through CSS selectors (but don&rsquo;t do it, since it makes fonts look terrible; it could be useful for icon fonts.)</li>
  1262. <li>3 colors × 8-bit subpixels = 2^8 × 3 = 3 bytes per pixel in uncompressed images.</li>
  1263. </ul>
  1264. <h3 id="colors-in-html-32">Colors in HTML 3.2</h3>
  1265. <ul>
  1266. <li><code>#rrggbb</code> hex syntax
  1267. <ul>
  1268. <li>Using hex syntax as a mental model for color is difficult, try playing <a href="">whatthecolor</a>.</li>
  1269. </ul>
  1270. </li>
  1271. <li>Useless color names that were based on the <a href="">Microsoft Windows default 16-color palette</a></li>
  1272. </ul>
  1273. <h3 id="colors-in-css-1---21">Colors in CSS 1 - 2.1</h3>
  1274. <ul>
  1275. <li><code>rgb()</code> syntax</li>
  1276. <li><code>#rgb</code> shortened hex syntax</li>
  1277. <li>&ldquo;orange&rdquo; color name (<a href="">seriously</a>)</li>
  1278. </ul>
  1279. <h3 id="css-color-level-3httpwwww3orgtrcss3-color"><a href="">CSS Color Level 3</a></h3>
  1280. <ul>
  1281. <li>A color space has <strong>perceptual uniformity</strong> when the perceptual similarity of two colors is measured by the distance between them.</li>
  1282. <li>RGB and RGB-derived color spaces <strong>are not</strong> perceptually uniform.</li>
  1283. <li>Everyone says &ldquo;CSS3&rdquo; even though it doesn&rsquo;t exist (only the modules are versioned).</li>
  1284. <li>HSL colors are slightly more intuitive than RGB colors.
  1285. <ul>
  1286. <li><strong>Saturation:</strong> Closeness to gray.</li>
  1287. <li><strong>Lightness:</strong> Closeness to white or black (but the model treats pure blue and pure yellow as having the same lightness, even though yellow always appears lighter to us; HSL is not perceptually uniform since it&rsquo;s derived from RGB.)</li>
  1288. </ul>
  1289. </li>
  1290. <li>The <code>hue-rotate</code> filter is useful for colorizing images when applied on top of a <code>sepia</code> filter.</li>
  1291. <li>The <code>multiply</code> blending mode tends to makes colors darker. (For example, red[255,0,0] × blue[0,0,255] = black[0,0,0,].)</li>
  1292. <li>Lightness != luminance, can&rsquo;t rely on it to judge whether white or black text would appear better on top of a color.
  1293. <ul>
  1294. <li>Play with contrast ratios at <a href=""></a>.</li>
  1295. </ul>
  1296. </li>
  1297. <li>CSS4 introduces relative luminance to better match human perception, but it&rsquo;s not perfect; it slightly fails for orange, but will always fail &ldquo;better&rdquo; than lightness (HSL).</li>
  1298. <li>When dealing with transparency, there&rsquo;s no such thing as a transparent pixel; transparency is calculated using <a href="">alpha blending</a>.</li>
  1299. <li>Using the <code>transparent</code> keyword is a shorthand for transparent <strong>black</strong>, so <code>linear-gradient(90deg, white, transparent)</code> will actually fade from gray instead of pure white. Use <code>hsla()</code> transparent white instead (<code>linear-gradient(90deg, white, hsla(0,0%,100%,0))</code>).</li>
  1300. <li>CSS Color Level 3 included some racist color names: <code>indianred</code>, <code>navajowhite</code>, and <code>peru</code></li>
  1301. <li>CSS Color Level 3 also included a color named <code>darkgray</code> which is actually lighter than <code>gray</code>, due to backwards compatibility (<code>gray</code> is halfway between white and black in RGB.)</li>
  1302. <li>The <a href=""><code>currentcolor</code> keyword</a> is the first variable we ever got in CSS.</li>
  1303. </ul>
  1304. <h3 id="the-future-css-color-module-level-4httpdevw3orgcsswgcss-color-4">The Future: <a href="">CSS Color Module Level 4</a></h3>
  1305. <ul>
  1306. <li><code>gray(%, alpha)</code> function</li>
  1307. <li><code>#rgba</code> and <code>#rrggbbaa</code></li>
  1308. <li><a href="">HWB (hue, whiteness, blackness) color model</a> (NOT the same as HSB).</li>
  1309. <li><a href=""><code>color()</code> function and adjusters</a></li>
  1310. <li>Named hues and <code>&lt;angle&gt;</code> in <code>hsl()</code></li>
  1311. <li><code>rgb()</code> and <code>hsl()</code> will accept alpha values</li>
  1312. <li><a href=""></a> is a relatively new CSS preprocessor that acts as a &ldquo;CSS polyfill&rdquo;, allowing the use of some of these future features today.</li>
  1313. </ul>
  1314. <h3 id="cmyk-vs-rgb">CMYK vs. RGB</h3>
  1315. <ul>
  1316. <li>CMY &ldquo;works&rdquo; mathematically but not in the real world, that&rsquo;s why CMYK is used for print.</li>
  1317. <li>sRGB has a slightly larger color gamut than CMYK (LAB &gt; Adobe RGB &gt; sRGB &gt; CMYK)</li>
  1318. <li>There&rsquo;s no simple way to convert between RGB and CMYK.</li>
  1319. </ul>
  1320. <hr>
  1321. <h2 id="josh-clark---mind-the-gap-designing-in-the-space-between-devices-globalmoxiecomhttpglobalmoxiecom-bull-globalmoxiehttpstwittercomglobalmoxie">Josh Clark - Mind the Gap: Designing in the Space Between Devices (<a href=""></a> • <a href="">@globalmoxie</a>)</h2>
  1322. <h3 id="physical-gap">Physical Gap</h3>
  1323. <ul>
  1324. <li>We&rsquo;ve lost the ability to transfer information between two physically collocated devices; we&rsquo;re in a multi-device world individually. (An old example: Palm Pilot beaming.)</li>
  1325. <li>Designers haven&rsquo;t provided an elegant strategy to cross the physical gap; right now all we have is remote control, self-email or SMS, and content syncing.</li>
  1326. </ul>
  1327. <h3 id="behavior-gap">Behavior Gap</h3>
  1328. <ul>
  1329. <li>How can we make physical interactions for exchanging data between devices?</li>
  1330. <li><strong>Sequenced:</strong> Move from one device to the other, e.g. desktop to mobile.</li>
  1331. <li><strong>Simultaneous:</strong> Live peer-to-peer interaction (for example, <a href="">Racer</a>).</li>
  1332. <li>It&rsquo;s not enough to share content across devices. Share action.</li>
  1333. <li>Sync verbs, not just nouns.</li>
  1334. <li>Current technologies: WebSockets, WebRTC, Bluetooth LE, Web Audio API, Infrared</li>
  1335. <li><strong>Danger:</strong> Screens encumber and constrain. Design for people, not screens. The best things in life happen outside of screens. It&rsquo;s our obligation to bend technology to our lives, not vice versa.</li>
  1336. </ul>
  1337. <h3 id="physical-interaction">Physical Interaction</h3>
  1338. <ul>
  1339. <li>Do we need screens at all? (For example, <a href="">Drumpants</a> doesn&rsquo;t.)</li>
  1340. <li>Drumpants uses human → device interaction, how do we bring that to device → device interaction?</li>
  1341. <li>The <a href="">Misfit Shine</a> fitness tracker syncs to your phone by placing it directly on the screen.
  1342. <ul>
  1343. <li>It turns out this is because the Shine is made of metal which significantly weakens its Bluetooth signal, so the Shine needs to be physically close to the phone to sync.</li>
  1344. <li>Embracing a constraint can lead to the best designs.</li>
  1345. </ul>
  1346. </li>
  1347. <li>If you physically tap your phone on your computer, nothing happens. Or does it? (See Happy Together&rsquo;s <a href="">demo video</a> and <a href="">code</a>.)</li>
  1348. <li>This is not a challenge of technology; it&rsquo;s a challenge of imagination.</li>
  1349. <li>There is magic in the gaps between devices. (See the <a href="">Grab Magic demo video</a>.)</li>
  1350. <li>Magic tends to decay; it is self-deprecating, we get used to it, and it&rsquo;s a moving target.</li>
  1351. <li>Never ever ever ever try to out-mouse the mouse.
  1352. <ul>
  1353. <li>For example, using the <a href="">LeapMotion</a> as a mouse is a much worse experience than just using a mouse.</li>
  1354. <li>However, the LeapMotion can be used to add digital magic to physical objects. (Example: pointing at floors in a physical model of a building highlights different floor plans with lights.)</li>
  1355. </ul>
  1356. </li>
  1357. <li><strong>Mundane computing:</strong> Making mundane tasks easier. (But perhaps you can go too far, given the example of the <a href="">Egg Minder</a>.)</li>
  1358. <li>Anything that can be connected will be connected; everyday objects will become digital gadgets.</li>
  1359. <li>Physical things have digital avatars.</li>
  1360. <li>Software makes hardware scale.
  1361. <ul>
  1362. <li><a href="">Teddy Ruxpin</a> looks creepy today, and relied on canned audio tapes. <a href="">Toymail</a> is a modern technical successor that allows for social interaction.</li>
  1363. <li><a href="">LG HomeChat</a>: Text your appliances!</li>
  1364. </ul>
  1365. </li>
  1366. <li><strong>Danger:</strong> Connected devices won&rsquo;t always say nice things. Anything that can be hacked will be hacked. (Cam you imagine an appliance botnet? Or an instant poltergeist?)
  1367. <ul>
  1368. <li><a href="">BBC article</a>: &ldquo;A luxury toilet controlled by a smartphone app is vulnerable to attack, according to security experts.&rdquo;</li>
  1369. </ul>
  1370. </li>
  1371. <li>Software is ideology, embedded with values.</li>
  1372. </ul>
  1373. <h3 id="imagination">Imagination</h3>
  1374. <ul>
  1375. <li>Plan for gadget hopping</li>
  1376. <li>Share action</li>
  1377. <li>Peer-to-peer sharing</li>
  1378. <li>Offscreen interactions</li>
  1379. <li>Design for sensors</li>
  1380. <li>Avatars for objects</li>
  1381. </ul>
  1382. <hr>
  1383. <h2 id="bruce-lawson---web-can-the-web-win-the-war-against-native-without-losing-its-soul-brucelawsoncoukhttpwwwbrucelawsoncouk-bull-brucelhttpstwittercombrucel">Bruce Lawson - Web+: Can the Web Win the War Against Native Without Losing its Soul? (<a href=""></a> • <a href="">@brucel</a>)</h2>
  1384. <ul>
  1385. <li>Why the web-vs-native gap? 86% of time is spent in apps rather than the mobile web.</li>
  1386. <li>Forget AppCache, <a href="">Service Workers</a> are the new hotness.
  1387. <ul>
  1388. <li>Invoked even when offline, can enable apps that are &ldquo;offline by default&rdquo;.</li>
  1389. <li>Normal resource loading is the fallback behavior.</li>
  1390. <li>Forces you to have URLs.</li>
  1391. <li>Service Workers + IndexedDB = Power.</li>
  1392. </ul>
  1393. </li>
  1394. <li>High-level or low-level?
  1395. <ul>
  1396. <li>&ldquo;&hellip;when we try to produce high-level APIs, they tend to suck for various reasons, and therefore that we should produce lower-level primitives atop which people can build nicer things&rdquo; -<a href="">Robin Berjon</a> (W3C, HTML Editor)</li>
  1397. <li>&ldquo;&hellip;browser vendors should provide new low-level capabilities that expose the possibilities of the underlying platform as closely as possible. They should also seed the discussion of high-level APIs through JavaScript implementations of new features&rdquo; -The <a href="">Extensible Web Manifesto</a></li>
  1398. </ul>
  1399. </li>
  1400. <li><a href="">BBC</a>: &ldquo;since the launch of iPlayer the amount of platforms with incompatible distribution infrastructure, video formats and security technologies has rapidly increased. This level of growth in the complexity of delivery is unsustainable&rdquo;
  1401. <ul>
  1402. <li>Perfect argument to promote web over native, hence DRM for the web is a necessary evil.</li>
  1403. <li>Allow the battle for DRM to win the war for the web (over native).</li>
  1404. </ul>
  1405. </li>
  1406. <li>People prefer the familiar; users trust known resources.</li>
  1407. <li>Bookmarks in mobile browsers are used sparingly, instead mobile users &ldquo;bookmark&rdquo; by downloading the native app.</li>
  1408. <li>What&rsquo;s the difference between &ldquo;bookmarking&rdquo; a page and &ldquo;installing&rdquo; it? Making it visible outside the browser.</li>
  1409. <li>Native apps feel native to the device/platform, web apps don&rsquo;t. Android and iOS are gradually developing different conventions for interaction, and a native app responds the way its user expects.</li>
  1410. <li><a href="">W3C Resource Priorities spec</a> — <code>&lt;img lazyload /&gt;</code></li>
  1411. <li>On mobile, hardware-accelerated scrolling gets knocked back down to software/the CPU if the browser has to listen for scroll events.</li>
  1412. <li>For the web to get a leg up on native, we need univerally installable webapps.
  1413. <ul>
  1414. <li>No versioning, no installing, instantaneous updates à la Google Chrome</li>
  1415. <li>&ldquo;I don&rsquo;t care which [standard] we end up using, I only care that we all end up using the same one.&rdquo;</li>
  1416. <li><a href="">Installable Webapps: Extend the Sandbox</a></li>
  1417. </ul>
  1418. </li>
  1419. <li>Using plain HTML for the initial page load will always be faster than JavaScript solutions.
  1420. <ul>
  1421. <li>There are tools like <a href=""></a>, but do you really want to go down that path?</li>
  1422. </ul>
  1423. </li>
  1424. <li>Don&rsquo;t make webapps that emulate all of the failures of native apps.</li>
  1425. </ul>
  1426. <hr>
  1427. <h1 id="scott-berkun---how-to-champion-ideas-back-at-work-scottberkuncomhttpwwwscottberkuncom-bull-berkunhttpstwittercomberkun">Scott Berkun - How to Champion Ideas (Back at Work) (<a href=""></a> • <a href="">@berkun</a>)</h1>
  1428. <ul>
  1429. <li>The real designer is the person with the power to make decisions.</li>
  1430. <li>There are more designers now who have founded a company than ever before in history.</li>
  1431. <li>Staying connected helps you champion ideas.</li>
  1432. <li>When an event is over, your chance to network and connect ends.</li>
  1433. <li><strong>Halfmeet:</strong> A person who you almost started a friendship with at an event. (You can guess what a <em>halfhook</em> is.)</li>
  1434. <li>5 non-slimy networking tricks:
  1435. <ul>
  1436. <li>Ask everyone you like for a business card</li>
  1437. <li>Saying thank you starts a conversation</li>
  1438. <li>Post your notes from sessions during the event — attracts people to you</li>
  1439. <li>Be active on Twitter to find outgoing people</li>
  1440. <li>If you use LinkedIn, write something personal</li>
  1441. </ul>
  1442. </li>
  1443. <li>Speakers love people who ask them thoughtful questions about their presentation.</li>
  1444. <li>Keep the fire burning — start a UX happy hour! Monthly booze is magical.</li>
  1445. <li>When trying to champion something, don&rsquo;t be an easy target. Don&rsquo;t shoot yourself or get shot.</li>
  1446. <li>Events are abstractions, but your life is <strong>specific</strong>.</li>
  1447. <li><a href="">Min/max note taking</a>:
  1448. <ul>
  1449. <li>You won&rsquo;t remember much in a week</li>
  1450. <li>You won&rsquo;t return to the slides</li>
  1451. <li>You need to capture reflections <strong>TODAY</strong></li>
  1452. <li>5 bullets per talk</li>
  1453. <li>Note links and references</li>
  1454. <li>Post a summary on your blog (or tweet it)</li>
  1455. <li>Post it at work / share with your boss</li>
  1456. </ul>
  1457. </li>
  1458. <li>Championing something requires a great deal of persuasion and charm; it&rsquo;s not what you say, it&rsquo;s what people hear.
  1459. <ul>
  1460. <li>Charm is designed and depends on context: &ldquo;Here&rsquo;s something you should be doing&rdquo; vs. &ldquo;Here&rsquo;s something that will help solve your problem&rdquo;.</li>
  1461. <li>Use language that matters to your audience.</li>
  1462. </ul>
  1463. </li>
  1464. <li>Progress is change; leaders like status quo and resist changes; therefore leaders resist progress. Powerful people want to protect their power.</li>
  1465. <li>Champions of ideas have really good networks.</li>
  1466. <li><a href="">How to convince your boss to try new things</a>:
  1467. <ul>
  1468. <li>Be awesome at your job</li>
  1469. <li>Get support from an influential coworker</li>
  1470. <li>Plan a trial, including how to evaluate</li>
  1471. <li>Pitch it</li>
  1472. <li>Do it awesomely</li>
  1473. <li>Repeat</li>
  1474. </ul>
  1475. </li>
  1476. </ul>
  1477. <hr>
  1478. <h1 id="conclusion-2">Conclusion</h1>
  1479. <p>Here are my takeaways from the conference:</p>
  1480. <ul>
  1481. <li>We design for people, not browsers. Worry about experience before worrying about technology decisions; don&rsquo;t miss the forest for the trees.</li>
  1482. <li>We need to go back to basics to improve performance, especially on mobile. Serve static, critical-path content as quickly as possible, then progressively enhance after the page is done loading.</li>
  1483. <li>Make an effort to effectively communicate about design in ways your coworkers and superiors  will understand and benefit from, so everyone wins.</li>
  1484. </ul>
  1485. <p>Finally, I have to mention that I was delighted to see that <a href="/2013/06/25/an_event_apart_boston_2013.html">last year&rsquo;s bacon cupcakes</a> made a welcome reappearance this year:</p>
  1486. <p><img src="/post_assets/2014/05/aea_boston_2014_bacon_cupcake.jpg" alt="Bacon Cupcake"></p>
  1487. <p>As always, An Event Apart was well-organized, informative, and served as a terrific inspirational recharge.</p>
  1488. ]]>
  1489.    </content>
  1490.  </entry><entry>
  1491.    <title>Configuring SSH and SCP/SFTP on DSM 5.0 for Synology DiskStations</title>
  1492.    <link rel="alternate" type="text/html" href="" />
  1493.    <id>,2014:/2014/04/12/configuring_ssh_and_scp_sftp_on_dsm_5.0_for_synology_diskstations.html</id>
  1494.    <published>2014-04-12T00:00:00-05:00</published>
  1495.    <updated>2014-04-12T00:00:00-05:00</updated>
  1496.    <author>
  1497.      <name>Josh Dick</name>
  1498.      <uri></uri>
  1499.    </author>
  1500.    <content type="html" xml:lang="en">
  1501.        <![CDATA[<blockquote>Because geeky toys never work quite right out of the box.</blockquote><h2 id="introduction">Introduction</h2>
  1502. <p>After a few years of waffling back and forth over whether I really needed a NAS, I finally decided to buy one. After doing some research, the option that seemed best for my needs was the <a href="">Synology DS214+</a>. Synology DiskStation NASes run a Linux-based operating system called Synology DiskStation Manager (DSM). Through sheer dumb luck, I happened to purchase the NAS exactly one month after the release of a new major version of the software, DSM 5.0. The NAS was a breeze to set up, including the including the installation of the two <a href="">3 terabyte Western Digital Red hard drives</a> I bought for it.</p>
  1503. <p>In general, the NAS&rsquo;s hardware and software are both great quality, but I ran into some issues after trying to interact with the NAS via SCP/SFTP. This article explains how to get SCP/SFTP working properly in DSM 5.0, exclusively using the stock software. This article assumes a basic knowledge of Linux and the DSM web interface, and thus has a corresponding level of detail. As far as I know, this information should apply to any Synology NAS running DSM 5.0, and was tested with DSM 5.0-4458 Update 2.</p>
  1504. <h2 id="enabling-services">Enabling Services</h2>
  1505. <p>DSM 5.0 includes two independent groups of service settings for SSH and SCP/SFTP.</p>
  1506. <p>Enable the SSH service by checking the Control Panel → &ldquo;Terminal &amp; SNMP&rdquo; menu → &ldquo;Terminal&rdquo; tab → &ldquo;Enable SSH service&rdquo; checkbox.</p>
  1507. <p>Enable the SFTP service (not to be confused with FTPS!) by checking the Control Panel → &ldquo;File Services&rdquo; menu → &ldquo;FTP&rdquo; tab → &ldquo;SFTP&rdquo; group → &ldquo;Enable SFTP service&rdquo; checkbox.</p>
  1508. <h2 id="enabling-ssh-users">Enabling SSH Users</h2>
  1509. <p>At this point, you should be able to successfully SSH to your NAS when authenticating as <code>root</code> or <code>admin</code>. Both users will have the password you chose for <code>admin</code> during setup. By default, those are the only two users that will be able to log in via SSH.</p>
  1510. <p>If you&rsquo;d like to enable SSH for other users, SSH in as root, and edit the file <code>/etc/passwd</code> with vi. Each user has a corresponding line in this file, and a user&rsquo;s shell setting appears at the end of a given line, after the last colon. Any user that has the the default shell setting <code>/sbin/nologin</code> won&rsquo;t be able to log in via SSH. To enable SSH for a given user, change their shell setting to match the shell setting for the root and admin users, which should be <code>/bin/sh</code>. Be careful when editing the <code>/etc/passwd</code> file; for our purposes here, you should only change the shell setting that appears after the last colon on a given line.</p>
  1511. <h2 id="enabling-the-user-home-service">Enabling the User Home Service</h2>
  1512. <p>Upon SSHing in as any user besides <code>root</code>, you might see a warning message (this example is for the &ldquo;admin&rdquo; user):</p>
  1513. <pre><code>Could not chdir to home directory /var/services/homes/admin: No such file or directory
  1514. </code></pre>
  1515. <p>This warning happens because home directories are controlled by DSM&rsquo;s &ldquo;user home service&rdquo;, which is disabled by default. To prevent the error, enable the user home service by checking the Control Panel → &ldquo;User&rdquo; menu → &ldquo;Advanced&rdquo; tab → &ldquo;User Home&rdquo; group → &ldquo;Enable user home service&rdquo; checkbox.</p>
  1516. <p>I recommend enabling the user home service even if you don&rsquo;t plan on using home directories, since leaving it disabled may cause some programs that rely on SCP/SFTP (<code>rsync</code>, etc) to abort with errors, regardless of which directory you&rsquo;re trying to manipulate.</p>
  1517. <p>By default, a given user&rsquo;s home directory is located at <code>/volume1/homes/username</code>.</p>
  1518. <h2 id="fixing-home-directory-permissions-for-ssh-public-key-authentication">Fixing Home Directory Permissions for SSH Public Key Authentication</h2>
  1519. <p>If you plan to use SSH public key authentication for a given user, the default permissions on user&rsquo;s home directories will prevent that. Making the permissions more restrictive (doing a <code>chmod 755</code> on a user&rsquo;s home directory as <code>root</code>) will allow SSH public key authentication to work properly. Of course, the user&rsquo;s <code>~/.ssh</code> folder and <code>~/.ssh/authorized_keys</code> file also need to have the correct permissions (<code>chmod 700</code> and <code>chmod 644</code>, respectively.)</p>
  1520. <h2 id="the-finish-line">The Finish Line</h2>
  1521. <p>After performing all of the aforementioned configuration tweaks, you should now have a painless SSH and SCP/SFTP experience with your Synology DiskStation NAS.</p>
  1522. <p>One final tip: I&rsquo;ve determined through experimentation that shared folders are served relative to the filesystem root (<code>/shared_folder</code>) when accessing the NAS via SFTP, but are served relative to the volume folder (<code>/volume1/shared_folder</code>) when using SCP. If specifying paths one way doesn&rsquo;t work, try the other way.</p>
  1523. ]]>
  1524.    </content>
  1525.  </entry><entry>
  1526.    <title>Everyday Carry</title>
  1527.    <link rel="alternate" type="text/html" href="" />
  1528.    <id>,2014:/2014/02/01/everyday_carry.html</id>
  1529.    <published>2014-02-01T00:00:00-05:00</published>
  1530.    <updated>2014-02-01T00:00:00-05:00</updated>
  1531.    <author>
  1532.      <name>Josh Dick</name>
  1533.      <uri></uri>
  1534.    </author>
  1535.    <content type="html" xml:lang="en">
  1536.        <![CDATA[<blockquote>What&rsquo;s in your pockets right now?</blockquote><p>What&rsquo;s in your pockets right now?</p>
  1537. <p>Maybe you have a bag with you, what&rsquo;s in there?</p>
  1538. <p>You may not have given too much thought to the things you carry around every day, but there is a term dedicated to the concept: &ldquo;everyday carry&rdquo;, or EDC.</p>
  1539. <p><a href="">Wikipedia defines everyday carry</a> better than I ever could (selections edited):</p>
  1540. <blockquote>
  1541. <p>Everyday carry refers to a small collection of tools, equipment and supplies that are carried on a daily basis to assist in tackling situations ranging from the mundane to the disastrous.</p>
  1542. <p>The term EDC also refers to the philosophy or spirit of &ldquo;preparedness&rdquo; that goes along with the selection and carrying of these items. Implicit in the term is the sense that an EDC is an individual&rsquo;s personal selection of equipment, arrived at after deliberation, rather than a standardized kit.</p>
  1543. <p>EDC items normally fit in pockets or a small pack, and/or are attached to clothing such as a belt. Emphasis is placed on the usefulness, accessibility and reliability of these items.</p>
  1544. </blockquote>
  1545. <p>EDC is a hobby of sorts, so it shouldn&rsquo;t be surprising that there <a href="">are</a> <a href="">many</a> <a href="">blogs</a> and even <a href="">entire communities</a> dedicated to the concept.</p>
  1546. <p>I&rsquo;ve always loved gadgets of all kinds, and thus gave lots of thought to my EDC long before I first heard the term.</p>
  1547. <p>Before reading any further, you should know that I don&rsquo;t consider myself to be an expert in any of the topics I&rsquo;m going to mention, just someone who is enthusiastic about EDC and who has done a fair bit of research. It&rsquo;s possible that there could be inaccuracies in what I&rsquo;ve written here; if you notice any, please <a href="">tell me</a>! My hope in writing this is to get you to think about your EDC and to offer some examples and resources along the way.</p>
  1548. <h2 id="why-care-about-everyday-carry">Why Care About Everyday Carry?</h2>
  1549. <p>My mentality has a lot to do with what <a href="">Dustin Curtis refers to as &ldquo;The Best&rdquo;</a>. Here are some relevant excerpts:</p>
  1550. <blockquote>
  1551. <p>&ldquo;The best&rdquo; isn&rsquo;t necessarily a product or thing. It&rsquo;s the reward for winning the battle fought between patience, obsession, and desire. It takes an unreasonably long amount of time to find the best of something. It requires that you know everything about a product&rsquo;s market, manufacture, and design, and that you can navigate deceptive pricing and marketing. It requires that you find the best thing for <em>yourself</em>, which means you need to know what actually matters to you.</p>
  1552. <p>If you&rsquo;re an unreasonable person, trust me: the time it takes to find the best of something is completely worth it. It&rsquo;s better to have a few fantastic things designed for you than to have many untrustworthy things poorly designed to please everyone. The result—being able to blindly trust the things you own—is intensely liberating.</p>
  1553. </blockquote>
  1554. <p>From an EDC perspective, &ldquo;the best&rdquo; doesn&rsquo;t necessarily mean &ldquo;the most expensive&rdquo; or &ldquo;the flashiest&rdquo;. To me, it means that each individual item in a person&rsquo;s EDC is the ideal realization of that item <em>for that person</em>. It also means that all of the items in a person&rsquo;s EDC should cohesively complement each other as the best possible EDC <em>for that person</em>. It means that the things a person carries with them every day should <em>deserve</em> to be carried every day.</p>
  1555. <p>For example, if you carry a wallet, is your wallet really &ldquo;the best&rdquo; wallet for you? Is it a <a href="">George Costanza wallet</a> that just needs to be cleaned out? Or maybe your wallet is bursting at the seams with plastic cards, and carrying a separate cardholder would make more sense? As another example, maybe finding your keys when you get home always ends up being an adventure in your bag, and then you end up fumbling with them in the dark? Could a better keychain and a small flashlight remove that small amount of frustration from your everyday life?</p>
  1556. <p>I am obsessed with removing frustrations like these, and that&rsquo;s why I care about finding &ldquo;the best&rdquo; EDC for myself. I try to keep my EDC as minimal as possible while still being functional. Being the gadget lover that I am, I also enjoy taking the time to put some thought and research into everything I carry.</p>
  1557. <p>All of that said, there&rsquo;s no such thing as the &ldquo;perfect EDC&rdquo;. A person&rsquo;s EDC will naturally change and evolve over time to meet their needs, always working towards &ldquo;the best&rdquo; EDC for them. What&rsquo;s more, one person&rsquo;s ideal EDC certainly isn&rsquo;t going to be ideal for everyone. If you work in an office like I do, your EDC is probably going to look very different than that of someone who, for example, works on oil rigs.</p>
  1558. <h2 id="my-everyday-carry">My Everyday Carry</h2>
  1559. <p>Seeing others&rsquo; EDC is both informative and fascinating, not only because you can draw inspiration for your own EDC, but also because it&rsquo;s interesting to see the stories that people&rsquo;s possessions tell about them.</p>
  1560. <p>To that end, I&rsquo;ll go through my own current EDC in detail and explain some of the thinking behind it. Even so, my EDC is always changing and evolving over time. While I certainly carry different things or sets of things depending on the situation (for example, I bring a laptop messenger bag to work), I consider my &ldquo;EDC proper&rdquo; to be the things I carry almost all of the time, regardless of the situation or context.</p>
  1561. <p>Without any further ado, here&rsquo;s what it looks like:</p>
  1562. <p><img src="/post_assets/2014/02/edc_overall.jpg" alt="Josh&rsquo;s EDC"></p>
  1563. <p>So, what is all that stuff?</p>
  1564. <h3 id="wallet">Wallet</h3>
  1565. <p>I&rsquo;m not a fan of money clips, so I carry a wallet. My wallet is a <a href="">Park Sloper Senior from One Star Leather Goods</a>. I carry a few cards including credit/debit cards, insurance cards, and my driver&rsquo;s license. I also like carrying paper money if I happen to need it, but I avoid carrying coins. One Star Leather Goods is a one-man operation running out of Los Angeles, CA. This is what appears on <a href="">their Etsy people page</a>:</p>
  1566. <blockquote>
  1567. <p>&ldquo;Buy good things, own them for a long time.&rdquo;</p>
  1568. <p>That napkin wisdom is borrowed from the internets and it&rsquo;s message is the basis of my philosophy. Today&rsquo;s &ldquo;buy it cheap then throw it away&rdquo; consumer environment is unsustainable and largely irresponsible. Do your research, find something that suits your needs and is well made, pay a fair price for it and be rewarded by years of happy use. Support your local independent craftsman over a big box retailer and search out unique and well made items.</p>
  1569. <p>While I believe that &ldquo;the best things in life aren&rsquo;t things,&rdquo; the things that you do need should be pleasurable to use and pleasurable to look at: simple, functional, durable and beautiful. I have a somewhat obsessive desire for perfection and put a high value on items that are designed and executed to the highest standards&hellip;</p>
  1570. </blockquote>
  1571. <p>Sound familiar?</p>
  1572. <p>I love the Park Sloper Senior because it looks classy, it&rsquo;s an extremely high quality handmade piece, and it holds my cash and cards while also accommodating a notebook and pen, all without being too bulky. Its larger size makes it strictly a &ldquo;jeans back pocket&rdquo; wallet, which isn&rsquo;t for everyone, but One Star does make a <a href="">smaller, front-pocket-friendly</a> version of the Park Sloper. I like carrying a notebook and pen in order to use the <a href="">Bullet Journal system</a>, which I&rsquo;ve found works well for me—better than any productivity-related iPhone app I&rsquo;ve tried. I use a <a href="">Field Notes 48-page notebook</a> and a <a href="">Uni-Ball Style Fit pen</a> with a <a href="">0.7mm Jetstream refill</a>. Sometimes, I also carry a <a href="">0.7mm Uni-Ball Jetstream RT pen</a>. The Park Sloper easily accommodates the slim Style Fit (<a href="">thanks, Brad!</a>), but the Jetstream RT is too thick to fit into the Park Sloper. Uni-Ball&rsquo;s Jetstream series pens are cheap, write smoothly, and are <a href="">very highly regarded</a>. Most importantly, Jetstream ink dries quickly; as a lefty, ink doesn&rsquo;t smear all over my hand when I write.</p>
  1573. <p>Before arriving at the Park Sloper, in the past (going back a few years—I don&rsquo;t buy wallets frequently and don&rsquo;t want to have to), I&rsquo;ve also tried:</p>
  1574. <ul>
  1575. <li>An <a href="">Aluminum Plate Wallet from Obstructures</a> which was obviously extremely durable, and had a cool gimmick/novelty factor. In practice, though, it ended up being awkward to quickly access cash and cards, which is an essential feature for a wallet.</li>
  1576. <li>A <a href="">Note Sleeve wallet from Belroy</a>, which was well-made and not too bulky, but whose lining eventually wore out and bled color onto some of my cards.</li>
  1577. <li>A wallet from <a href="">Saddleback Leather</a>, which was also very high quality, but was too bulky for my taste. It seems to me that most of their practical wallet designs have similar bulkiness problems, and their thinner designs are too minimal.</li>
  1578. <li>A <a href="">nylon wallet from All-Ett</a>, which is probably the slimmest wallet you can buy, but which wore out quickly because the material was so thin.</li>
  1579. </ul>
  1580. <h3 id="watch">Watch</h3>
  1581. <p><img src="/post_assets/2014/02/edc_watch.jpg" alt="Halios Tropik SS Watch"></p>
  1582. <p>I&rsquo;ve always loved watches. With today&rsquo;s ubiquitous mobile phones, many people no longer bother wearing a watch, but I can&rsquo;t picture myself without one. I especially love mechanical watches (as in &ldquo;no electricity involved&rdquo;), although they certainly don&rsquo;t keep time as accurately as quartz watches. I think there&rsquo;s something special about keeping a tiny, intricate, dependable machine on your wrist, with you always.</p>
  1583. <p>When it comes to the outward look and design of a watch, I&rsquo;m a fan of understated simplicity. I&rsquo;ve gone through far too many watches to list here, and wear different ones depending on my mood, but here are my current three favorites:</p>
  1584. <ul>
  1585. <li>The watch in the picture is the <a href="">Halios Tropik SS</a>. It&rsquo;s a very high-quality piece and a beautiful work of art.</li>
  1586. <li>My other go-to watch is the <a href="">Techné GosHawk</a>, another high-quality piece that&rsquo;s more affordable than the Halios.</li>
  1587. <li>My &ldquo;beater&rdquo; watch, which I wear in situations I wouldn&rsquo;t want to expose the nicer mechanical watches to, is a <a href="">Casio G-Shock GWM5610-1</a>. I love the retro styling, the fact that it&rsquo;s solar powered (and hence never needs battery changes), and that it has the ability to set itself using atomic clock radio signals. The watch has been put through its paces and still looks great.</li>
  1588. </ul>
  1589. <p>If you&rsquo;re intrigued by mechanical watches but have reservations about buying one, they don&rsquo;t necessarily have to break the bank—the <a href="">Seiko SNK809</a> is a great entry-level automatic (self-winding) mechanical watch. If you want to learn more about the world of watches in general, this <a href="">excellent primer from Everyday Commentary</a> is a great place to start.</p>
  1590. <h3 id="tools-gadgets-and-keys">Tools, Gadgets, and Keys</h3>
  1591. <p>Tools and gadgets encompass what is probably the largest rabbit hole as far as EDC is concerned; there are an overwhelming number of EDC-related tools—and options for carrying tools—available on the market.</p>
  1592. <h4 id="pocket-danglerssuspension-clips">Pocket Danglers/Suspension Clips</h4>
  1593. <p>Gadgets known as &ldquo;pocket danglers&rdquo; or &ldquo;suspension clips&rdquo; are popular among EDC enthusiasts. These gadgets provide a way of attaching tools/keys/other gadgets to them, and hang from a pocket or belt loop. The idea behind them is that they &ldquo;suspend&rdquo; attached items in the middle of a pocket in order to prevent those items from awkwardly bunching up at the bottom of a pocket. Suspension clips and pocket danglers often double as tools themselves.</p>
  1594. <p>I currently use a <a href="">TT PocketTTools 69 Dangler Tool</a>, which doubles as a bottle opener and cap twist assist. Although I don&rsquo;t use the twist assist, it&rsquo;s handy to always have a bottle opener on my belt loop. I love that the dangler is designed in such a way that its use as a bottle opener isn&rsquo;t obstructed by the items attached to it. I&rsquo;ve tried a few other danglers/suspension clips in the past:</p>
  1595. <ul>
  1596. <li>The <a href="">Corter Leather Bottle Hook</a>, another bottle-opening belt loop keychain. I really like the Bottle Hook, but the 69 dangler  does a better job of evenly spreading out attached items inside a pocket. The Bottle Hook is also larger than the 69 dangler, which causes attached items to sit comparatively lower in a pocket.</li>
  1597. <li>The <a href="">Gamble Made GearPull Dangler</a>, which I <a href="">backed on Kickstarter</a> on a whim since it looked interesting. Like the 69 Dangler, the GearPull does a decent job of evenly spreading out attached items inside a pocket. Unlike the 69 Dangler, I was constantly afraid that the GearPull would fall off my pants. Its clip mechanism has a large gap that causes it to sit uncomfortably loosely on a pocket (or at least on my pocket.)</li>
  1598. <li>The <a href="">TEC Accessories P-7 Suspension Clip</a>. This clip has the most minimal design of the ones I&rsquo;ve listed. At $12 as of this writing, I think the clip is expensive for what it is. It didn&rsquo;t hold up well for me in the long term; the steel gradually bent until it had the same looseness problem as the GearPull.</li>
  1599. </ul>
  1600. <p>My tools and gadgets are attached to the 69 dangler using a combination of common split rings and <a href="">TEC Accessories 15 mm Pico Gate Clips</a>. All of the attached tools can be easily removed from the dangler without fiddling with split rings. The tiny gate clips perfectly fit into the dangler&rsquo;s holes and are used to attach tools that don&rsquo;t provide their own detaching/quick release mechanism. All other tools are directly attached to the dangler with split rings.</p>
  1601. <h4 id="tools-on-the-69-dangler">Tools On the 69 Dangler</h4>
  1602. <p><img src="/post_assets/2014/02/edc_tools.jpg" alt="Josh&rsquo;s EDC Tools"></p>
  1603. <p>From top to bottom, these are the items attached to the 69 dangler:</p>
  1604. <ul>
  1605. <li><a href="">Leatherman Micra Multi-Tool</a>. The Micra includes a whole bunch of tools but I primarily use its knife and scissors.</li>
  1606. <li><a href="">Prometheus Lights Beta-QR in Electroless Nickel</a>. For the money, I believe this is the best keychain flashlight on the market right now. It&rsquo;s   very high quality and durable, looks great, has decent light output, uses a <a href="">high-CRI emitter</a>, and is powered by a standard AAA battery. It also has an ingeniously simple quick-release mechanism.</li>
  1607. <li><a href="">County Comm &ldquo;Split Pea&rdquo; Peanut Lighter</a>. This lighter is essentially a tiny Zippo; it uses lighter fluid rather than butane. It is comprised of two halves that screw together with an O-ring between them, ensuring that lighter fluid doesn&rsquo;t leak or evaporate. I don&rsquo;t smoke, but I carry the lighter because it&rsquo;s cheap, tiny, interesting, and could be useful in a pinch.</li>
  1608. <li><a href="">Nite Ize DoohicKey One-Piece Multitool</a>. Its ruler and bottle opener might be redundant among the other tools, but it works great for light prying tasks and for opening boxes. I like its slim profile and the fact that it has its own integrated spring clip. Since it costs about $5, buying one is a no-brainer.</li>
  1609. <li><a href="">LaCie Porsche Design USB Key</a>. I&rsquo;ve  used, abused, and destroyed more flash drives over the years than I can count. Before this flash drive, I carried the <a href="">Kingston Data Traveler SE9</a>. Both flash drives are slim, reasonably priced, and have metal enclosures that can generally survive being knocked around with the other tools on the dangler. Although it&rsquo;s not the fastest flash drive on the market, the LaCie unit is USB 3.0 while the Kingston is USB 2.0. Also, the Kingston&rsquo;s USB circuit board is simply glued in to its metal enclosure, and the glue eventually failed for me, yielding an empty metal skeleton along with a bare circuit board. I haven&rsquo;t had any issues with the LaCie so far.</li>
  1610. </ul>
  1611. <h3 id="miscellaneous">Miscellaneous</h3>
  1612. <p>There are a few other things I carry that don&rsquo;t need much elaboration:</p>
  1613. <ul>
  1614. <li><a href=",default,pd.html?cgid=lipbalm&amp;start=2&amp;q=#start=2">Burt&rsquo;s Bees Beeswax Lip Balm</a>. I have perpetually dry lips year round, and the &ldquo;cool burn&rdquo; sensation of beeswax lip balm helps. I always peel the label off the Burt&rsquo;s Bees stick whenever I start using a new one; otherwise, excess adhesive around the label collects pocket lint and looks gross.</li>
  1615. <li>Two <a href="">EpiPens</a> along with <a href="">Benadryl</a> tablets in a <a href="">Kozyepi case</a> (not pictured). I have a nut allergy and carry these for emergency use.</li>
  1616. <li><a href="">Apple iPhone 5S</a> smartphone in a black <a href="">Magpul Field Case</a>. My iPhone is like a third arm for me. The Magpul case is reasonably priced, excellent quality, and fits the phone like a glove. Magpul also makes a similar, beefier case called the <a href="">Bump Case</a>, but I don&rsquo;t need the additional protection or bulk. I previously used <a href="">Apple&rsquo;s own leather iPhone 5S case</a> in black, and while the case was well constructed, the leather scratched very easily.</li>
  1617. <li>The <a href="">Misfit Shine</a> fitness tracker. It&rsquo;s an interesting little device. Because I only use it as a pedometer, the fact that I carry an iPhone 5S that works with <a href="">David Smith&rsquo;s</a> excellent, free <a href="">Pedometer++ App</a> makes the Shine somewhat redundant. The Shine&rsquo;s automatic iPhone sync also doesn&rsquo;t work reliably for me. Despite all of that, it fits in the coin pocket of my jeans and certainly isn&rsquo;t weighing me down or getting in the way, so it&rsquo;s still part of my EDC.</li>
  1618. <li>An orange <a href="">Monkey Knuts Knut Buster Keychain</a> with five keys. <a href="">Gadgets</a> <a href="">for</a> <a href="">carrying</a> <a href="">keys</a> <a href="">abound</a> <a href="">on</a> <a href="">Kickstarter</a> <a href="">and</a> <a href="">elsewhere</a>. I&rsquo;ve realized over time that I don&rsquo;t really need to keep keys with all the time, so I&rsquo;ve more or less ignored most key-carrying solutions. One notable exception for me is the <a href="">BladeKey Bolt</a>, which worked great when I regularly included keys as part of my EDC. The large monkey fist knot on the Knut Buster I use now makes it easy to grab my keys when I actually do need them.</li>
  1619. </ul>
  1620. <p>&hellip;And there you have it: my EDC explained in painstaking detail. As you can see, I&rsquo;ve put a lot of thought (and over time, a pretty penny) into my EDC, and it is constantly evolving.</p>
  1621. <h2 id="other-thoughts-on-tools-and-gadgets">Other Thoughts on Tools and Gadgets</h2>
  1622. <p>There are several types/categories of tools I used to carry that have either been displaced by what I&rsquo;m carrying now, or that I discovered I can get along just fine without. There are hundreds or even thousands of tools available on the market in each of these categories, made by both production manufacturers and smaller, custom manufacturers or individuals.</p>
  1623. <p>Needless to say, researching and choosing tools in these categories can easily be overwhelming.</p>
  1624. <p>Most of these categories have Internet communities dedicated to them, which can help with research. Although I don&rsquo;t participate directly in most of the communities I&rsquo;m going to mention, I&rsquo;ve discovered them through Google and other Internet EDC research.</p>
  1625. <h3 id="flashlights">Flashlights</h3>
  1626. <p>I&rsquo;ve carried flashlights for a very long time. I use them constantly, whether it&rsquo;s for doing something outdoors at night or for being able to see better in tight spots behind computers. For a while, I liked carrying a pocket-sized clip-on flashlight as part of my EDC, but I eventually realized clip-on flashlights generally produced more light than I needed in most situations, and therefore weren&rsquo;t worth the space they occupied in my pocket.</p>
  1627. <p>Before I added the aforementioned <a href="">Prometheus Lights Beta-QR</a> to my EDC, I carried a <a href="">Veleno Designs/Steve Ku Quantum D2</a>. The D2 is <strong>tiny</strong>, which is both a good and bad thing. Its small size makes it easy to carry, and it has great light output for its size. However, it uses an obscure type of rechargeable lithium ion battery (which needs to be recharged fairly often due to its size.) I ended up switching to the Beta-QR since it&rsquo;s still a manageable size and uses a standard AAA battery (NiMH rechargeable or alkaline), both of which are much more readily available and have higher capacities than the D2&rsquo;s battery, and therefore less likely to let me down when I need to rely on the light.</p>
  1628. <p>If you want to do more research on flashlights, the predominant flashlight community on the Internet is <a href="">Candle Power Forums</a>. When researching flashlights, pay close attention to the type of batteries they use. A flashlight&rsquo;s batteries give you a general idea of its size and runtime. Additionally, some flashlights use slightly less common types of batteries such as <a href="">CR123 cells</a>, which could either be acceptable or negative depending on your needs.</p>
  1629. <p>Although there are dozens of flashlight manufacturers, some popular manufacturers in no particular order are <a href="">4Sevens</a>, <a href="">Fenix</a>, <a href="">EAGTAC</a>, and <a href="">Sunwayman</a>.</p>
  1630. <h3 id="knives">Knives</h3>
  1631. <p>I don&rsquo;t carry a knife for self-defense purposes; instead I carry one simply because a knife is handy to have around. I primarily use knives for opening bubble mailer envelopes, for opening and breaking down boxes, and for cutting cable ties. In a similar vein to flashlights, I&rsquo;ve gradually minimized my knife carry over time. (Do you see a trend here?) I used to carry  a folding knife but eventually realized I generally didn&rsquo;t need a folding knife on my person at all times. In combination, the aforementioned <a href="">Nite Ize DoohicKey</a> and <a href="">Leatherman Micra</a> work well for 90% of my cutting tasks. I still keep folding knives around (though not as part of my EDC) for everything else.</p>
  1632. <p>There&rsquo;s a lot to learn about knives, including types of blade steels and shapes, handle (&ldquo;scale&rdquo;) materials, locking mechanisms, and stropping and sharpening tools and techniques. As with flashlights, there are Internet knife communities such as <a href="">Blade Forums</a> and <a href="">Knife Forums</a> that can help with further research. Also as with flashlights, there are dozens of knife manufacturers. Some popular knife manufacturers, again in no particular order, include <a href="">SOG Knives</a>, <a href="">Columbia River Knife and Tool (CRKT)</a>, <a href="">Spyderco</a>, <a href="">Kershaw Knives</a>, <a href="">Benchmade</a>, and <a href="">Böker</a>.</p>
  1633. <p>Although I no longer regularly EDC a folding knife, I still have some favorites:</p>
  1634. <ul>
  1635. <li>The <a href="">Spyderco Techno</a> for its superior build quality, materials, and surprising carryability and ergonomics in spite of its relative thickness.</li>
  1636. <li>The <a href="">SOG Knives Flash I Straight Edge</a>  for its small size, its pocket clip that carries very deeply in a pocket so it won&rsquo;t fall out or get caught on something, and its spring-assisted opening, all while being affordable at around $30.</li>
  1637. <li>The <a href="">Benchmade 585 BK Mini-Barrage</a>, which I impulse purchased in person from a dealer without doing any prior research, because I got it at a great price, it oozes quality, and it has a very solid-feeling axis locking mechanism.</li>
  1638. <li>The <a href="">Böker Keycom</a>, which is probably the smallest frame-locking knife on the market today. It&rsquo;s decent quality, feels right at home on a keychain, and is very affordable at about $15. This was the last item to be removed from my EDC (I swapped it out for the <a href="">Leatherman Micra</a>.)</li>
  1639. <li>The <a href="">Spyderco Bug</a>, because it&rsquo;s both cheap and extremely small while still being useful. That said, it&rsquo;s a bit hard to open because of its size.</li>
  1640. </ul>
  1641. <h3 id="multitools">Multitools</h3>
  1642. <p>I personally categorize multitools into two distinct groups. The first group is what I would call &ldquo;conventional&rdquo; multitools such as <a href="">Leatherman&rsquo;s folding tools</a> or <a href="">Victorinox Swiss Army knives</a>. (I believe Swiss Army knives are better categorized as multitools rather than knives, but it&rsquo;s a matter of opinion.) The second group is what has come to be known as &ldquo;one-piece multitools&rdquo;, or &ldquo;OPMTs&rdquo;. OPMTs are generally milled from a single piece of metal and have no moving parts.</p>
  1643. <p>The predominant Internet multitool community is <a href=""></a>.</p>
  1644. <p>Similar to my thinking behind carrying a knife, I think multitools are simply handy to have around. Many multitools have an integrated knife which may be fine for your needs, and could eliminate the need to carry a separate, dedicated knife, which is what happened in my case.</p>
  1645. <p>I&rsquo;ve carried a few different multitools across both types, and in fact, still do: the <a href="">Leatherman Micra</a>, the <a href="">Nite Ize DoohicKey</a>, and the <a href="">TT PocketTTools 69 Dangler Tool</a>. (I would classify the DoohicKey as an OPMT even though it&rsquo;s not technically a single piece of metal.)</p>
  1646. <p>That said, I&rsquo;ve done the least amount of experimenting in the multitool category.</p>
  1647. <p>For a while I carried a <a href="">Victorinox Rambler</a> which I loved as a multitool, but which ended up getting beat up by the rest of my EDC gadgets to the point that it started bothering me. I also tried carrying a larger <a href="">Leatherman Sidekick</a>, which is reasonably affordable at about $30, but it ended up being too large and cumbersome for my own EDC purposes. I still keep it in the laptop bag I take with me to work. (If you like the Sidekick, you might also want to take a look at its brother, the <a href="">Leatherman Wingman</a>.)</p>
  1648. <p>In terms of OPMTs, <a href="">Atwood Knife and Tool</a> is probably the biggest name in the game. Peter Atwood makes and sells his own tools in batches on <a href="">his blog</a>. They usually sell out within minutes, and are often <a href=";_osacat=0&amp;_from=R40&amp;_nkw=atwood+tool&amp;_sacat=0">resold with a large premium on eBay</a>. I&rsquo;ve been lucky enough to be able to purchase a few OPMTs directly from Peter. While his tools are extremely well made, I no longer carry them as part of my EDC because I didn&rsquo;t use them often enough to justify their size and weight (and no, I still have them—I haven&rsquo;t resold them on eBay!)</p>
  1649. <p>Many other individuals make and sell OPMTs, such as the aforementioned <a href="">TT PockeTTools</a>, which I understand is also a single-man operation. Various bigger companies also sell OPMTs. Leatherman <a href="">has its own line</a>, and Gerber sells the <a href="">Shard Keychain Tool</a>, which is extremely affordable at about $6.</p>
  1650. <h2 id="in-conclusion">In Conclusion&hellip;</h2>
  1651. <p>I&rsquo;ve given you a detailed tour of my EDC, and I&rsquo;ve explained the thinking behind some of my past and present EDC choices. I&rsquo;ve also pointed out some resources that you can use to do your own EDC research.</p>
  1652. <p>EDC as a hobby can certainly be interesting and fun in and of itself, but don&rsquo;t take it <em>too</em> seriously—lots of EDC experimentation can get expensive quickly! Take some time to think about what works for you and what could be made better, then experiment.</p>
  1653. <p>Ultimately, your EDC is an expression of yourself, and should augment your day-to-day life. Get out there and live it!</p>
  1654. <hr>
  1655. <p><em>2014-02-02: Added information about the Uni-Ball Style Fit pen that was accidentally omitted.</em></p>
  1656. ]]>
  1657.    </content>
  1658.  </entry><entry>
  1659.    <title> Weather on the Mac Desktop</title>
  1660.    <link rel="alternate" type="text/html" href="" />
  1661.    <id>,2013:/2013/10/10/forecast.io_weather_on_the_mac_desktop.html</id>
  1662.    <published>2013-10-10T00:00:00-05:00</published>
  1663.    <updated>2013-10-10T00:00:00-05:00</updated>
  1664.    <author>
  1665.      <name>Josh Dick</name>
  1666.      <uri></uri>
  1667.    </author>
  1668.    <content type="html" xml:lang="en">
  1669.        <![CDATA[<blockquote>Because I could.</blockquote><p>When I saw that the excellent weather service <a href=""></a> released a feature called <a href="">Forecast Embeds</a>, I thought it would be neat to show the widget directly on my Mac&rsquo;s desktop. I whipped up a solution that ended up looking like this:</p>
  1670. <p><img src="/post_assets/2013/10/forecast_weather_example.png" alt=" Weather Example"></p>
  1671. <p>Read on to learn how get Forecast Embeds up and running on your Mac&rsquo;s desktop.</p>
  1672. <h2 id="dependencies">Dependencies</h2>
  1673. <ul>
  1674. <li><a href="">GeekTool</a>, <a href="">NerdTool</a>, or any other tool that can display an image directly on the desktop</li>
  1675. <li>The following command-line utilities, all of which are available via <a href="">Homebrew</a> on OS X:
  1676. <ul>
  1677. <li><a href="">webkit2png</a></li>
  1678. <li><a href="">ImageMagick</a></li>
  1679. </ul>
  1680. </li>
  1681. <li><a href=""><code></code></a>, a simple shell script I wrote</li>
  1682. </ul>
  1683. <h2 id="how-it-works">How it Works</h2>
  1684. <ul>
  1685. <li>On a reasonably slow interval, the <code></code> script automatically takes a screenshot of the Forecast Embeds page with the latest weather data, and stores that screenshot on the filesystem. It then does some image processing on the screenshot to make it look more attractive when overlaid onto a wallpaper.</li>
  1686. <li>On a reasonably fast interval, the screenshot is automatically [re-]displayed on the desktop.</li>
  1687. </ul>
  1688. <h2 id="getting-it-going">Getting it Going</h2>
  1689. <ol>
  1690. <li>
  1691. <p>Install the dependencies listed above, and grab a copy of the <a href=""><code></code> script</a>.</p>
  1692. </li>
  1693. <li>
  1694. <p>Edit the variables in <code></code> to your liking.</p>
  1695. <p>You&rsquo;ll need to provide the latitude/longitude for your area, which you can find using a service like <a href=""></a>. There are several available options that aren&rsquo;t part of the script, but can be added to the Forecast Embeds URL in the script. See the <a href="">Forecast Embeds documentation</a> for details.</p>
  1696. </li>
  1697. <li>
  1698. <p>Run <code></code> and verify that the image file <code>/tmp/weather-full.png</code> is created on your system, and contains the font/text/weather information you expect.</p>
  1699. </li>
  1700. <li>
  1701. <p>Embed the <code>/tmp/weather-full.png</code> image on your desktop using GeekTool (or your tool of choice.) I configured GeekTool to refresh the image every minute.</p>
  1702. </li>
  1703. <li>
  1704. <p>Make <code></code> automatically run on an interval (15 minutes seems reasonable). You can do this via GeekTool or <code>launchd</code>.</p>
  1705. </li>
  1706. <li>
  1707. <p>You&rsquo;re done.</p>
  1708. </li>
  1709. </ol>
  1710. <h2 id="final-thoughts">Final Thoughts</h2>
  1711. <p>Forecast Embeds are simple web pages that include animations, so the sceenshots that are taken will inevitably catch the animations mid-frame. If you prefer to keep the animations working, you can use something like <a href="">Fluid</a> to float the Forecast Embeds page on your desktop as its own app, but it won&rsquo;t be transparent and thus won&rsquo;t blend in with your wallpaper.</p>
  1712. ]]>
  1713.    </content>
  1714.  </entry><entry>
  1715.    <title>Making Git a Little Fuzzier</title>
  1716.    <link rel="alternate" type="text/html" href="" />
  1717.    <id>,2013:/2013/09/02/making_git_a_little_fuzzier.html</id>
  1718.    <published>2013-09-02T00:00:00-05:00</published>
  1719.    <updated>2013-09-02T00:00:00-05:00</updated>
  1720.    <author>
  1721.      <name>Josh Dick</name>
  1722.      <uri></uri>
  1723.    </author>
  1724.    <content type="html" xml:lang="en">
  1725.        <![CDATA[<blockquote>A command-line wrapper for Git that does fuzzy filename matching.</blockquote><p>As I wrote in a <a href="/2012/12/30/my_git_prompt_for_zsh.html">previous post</a>, I constantly use <a href="">Git</a> on the command line. The command line is simply the fastest and easiest way for me to work with Git.</p>
  1726. <p>That said, one understandable aspect of working with Git on the command line is that file/directory paths must be explicitly specified. This means that while in the middle of typing a Git command, I often end up needing to do one or both of the following:</p>
  1727. <ul>
  1728. <li>
  1729. <p>Move a hand from the keyboard to the mouse in order to select and copy a path from the output of <code>git status</code>, then return to the keyboard to paste the path</p>
  1730. </li>
  1731. <li>
  1732. <p><code>cd</code> to a random directory (usually aggressively ramming the tab key) in order to either get <code>git status</code> to spit out a copyable path, or at least low enough into the directory tree to be able to have <code>git &lt;git command&gt; .</code> manipulate the desired path(s)</p>
  1733. </li>
  1734. </ul>
  1735. <p>While neither of these take a long time, they&rsquo;re both annoying.</p>
  1736. <p>After searching for tools to attack this problem and not finding anything that worked well for me, I decided to create <a href=""><code>git-fuzzy</code></a>.</p>
  1737. <p><code>git-fuzzy</code> simply wraps normal Git commands and (for now) assumes that its last argument should be a path that should be fuzzy-completed.</p>
  1738. <p>So, instead of having to do something like:</p>
  1739. <pre><code> git add another/very/long/path/myawesomefile.ext
  1740. </code></pre>
  1741. <p><code>git-fuzzy</code> makes things pleasantly fuzzier:</p>
  1742. <pre><code> git fuzzy add awesome
  1743. </code></pre>
  1744. <p>The tool is tiny, basic and somewhat crude, but so far it gets the job done for me.</p>
  1745. <p><code>git-fuzzy</code> is <a href="">available on GitHub</a> and is <a href="">installable via <code>npm</code></a>.</p>
  1746. <p>If you end up using <code>git-fuzzy</code>, I&rsquo;d love to hear your thoughts about it.</p>
  1747. ]]>
  1748.    </content>
  1749.  </entry><entry>
  1750.    <title>An Event Apart Boston 2013</title>
  1751.    <link rel="alternate" type="text/html" href="" />
  1752.    <id>,2013:/2013/06/25/an_event_apart_boston_2013.html</id>
  1753.    <published>2013-06-25T00:00:00-05:00</published>
  1754.    <updated>2013-06-25T00:00:00-05:00</updated>
  1755.    <author>
  1756.      <name>Josh Dick</name>
  1757.      <uri></uri>
  1758.    </author>
  1759.    <content type="html" xml:lang="en">
  1760.        <![CDATA[<blockquote>My notes from An Event Apart, &ldquo;the design conference for people who make websites&rdquo;.</blockquote><p><img src="/post_assets/2013/06/aea_boston_2013_swag.jpg" alt="An Event Apart SWAG"></p>
  1761. <p><a href="">An Event Apart</a> bills itself as &ldquo;the design conference for people who make websites.&rdquo; <a href="/2012/08/19/an_event_apart_boston_2012.html">I attended last year</a>, and was very fortunate to be able to attend once again this year. Here are my notes in their entirety from <a href="">An Event Apart Boston 2013</a>. My notes are grouped by talk, in the order that each talk happened at the conference.</p>
  1762. <h1 id="day-1-62413">Day 1: 6/24/13</h1>
  1763. <h2 id="jeffrey-zeldman---the-ten-commandments-of-web-design-zeldmancomhttpwwwzeldmancom-bull-zeldmanhttpstwittercomzeldman">Jeffrey Zeldman - The Ten Commandments of Web Design (<a href=""></a> • <a href="">@zeldman</a>)</h2>
  1764. <h3 id="thou-shalt-entertain">Thou Shalt Entertain</h3>
  1765. <ul>
  1766. <li>Take the opportunity to entertain when the situation would otherwise disappoint. (Example: entertaining 404 pages. &ldquo;And why are we still calling them &lsquo;404 pages&rsquo;?&quot;)</li>
  1767. <li>Humanize the experience by adding little copy touches (e.g. the <a href="">dynamic multi-lingual greeting</a> on Flickr&rsquo;s old site.)</li>
  1768. </ul>
  1769. <h3 id="test-everything-including-assumptions">Test Everything (Including Assumptions)</h3>
  1770. <ul>
  1771. <li>Test your work on as many devices as possible (for example, by using tools from Adobe, or open-source tools like <a href="">Remote Preview</a>)</li>
  1772. <li>Challenge your own assumptions, don&rsquo;t work in isolation.</li>
  1773. </ul>
  1774. <h3 id="thou-shalt-iterate">Thou Shalt Iterate</h3>
  1775. <ul>
  1776. <li>Sometimes inspiration comes from just working a lot and being dissatisfied.</li>
  1777. <li>&ldquo;I move things around until they look right.&rdquo; —Milton Glaser</li>
  1778. </ul>
  1779. <h3 id="thou-shalt-ship">Thou Shalt Ship</h3>
  1780. <ul>
  1781. <li>If you can&rsquo;t delegate at the pixel level, you&rsquo;ll never ship.</li>
  1782. <li>NOT shipping is great for consultants.</li>
  1783. </ul>
  1784. <h3 id="engage-thy-community">Engage Thy Community</h3>
  1785. <ul>
  1786. <li>Interact with customers and humanize your company rather than just selling product.</li>
  1787. <li><a href="">Embeddable comments</a> drive traffic between your site and other sites while engaging the community.</li>
  1788. </ul>
  1789. <h3 id="love-thy-user-as-thyself">Love Thy User As Thyself</h3>
  1790. <ul>
  1791. <li>Just give the user what they want, where they want, without dumbing anything down.</li>
  1792. </ul>
  1793. <h3 id="remember-the-content-and-keep-it-holy">Remember The Content And Keep It Holy</h3>
  1794. <ul>
  1795. <li>Get the right content to the right user at the right time.</li>
  1796. <li>Anything in the design that detracts from that should be cut; remove every distraction you possibly can.</li>
  1797. </ul>
  1798. <h3 id="thou-shalt-make-magic">Thou Shalt Make Magic</h3>
  1799. <ul>
  1800. <li>Make magic. Don&rsquo;t try for perfection.</li>
  1801. <li>Instagram had a horrible web experience but was successful because they did one thing very well: their app.</li>
  1802. </ul>
  1803. <h3 id="thou-shalt-prioritize">Thou Shalt Prioritize</h3>
  1804. <h3 id="to-thine-own-self-be-true">To Thine Own Self Be True</h3>
  1805. <ul>
  1806. <li>Don&rsquo;t make improvements for their own sake if they&rsquo;re not really improvements.</li>
  1807. <li>Don&rsquo;t change for the sake of change, or try to be something you&rsquo;re not, have a reason for every change you make.</li>
  1808. </ul>
  1809. <h3 id="this-is-design-not-religion">This is design, not religion.</h3>
  1810. <hr>
  1811. <h2 id="jake-archibald---rendering-without-the-lumpy-bits-jakearchibaldcomhttpjakearchibaldcom-bull-jaffathecakehttpstwittercomjaffathecake">Jake Archibald - Rendering Without the Lumpy Bits (<a href=""></a> • <a href="">@jaffathecake</a>)</h2>
  1812. <ul>
  1813. <li>Graphics performance: The new developer challenge.</li>
  1814. <li>Until recently, the goal was for graphics performance to be <em>usable</em> (but not necessarily &ldquo;good&rdquo;).</li>
  1815. <li>Browsers maintain a render tree that parallels the DOM. Changes to the render tree cause reflows.
  1816. <ul>
  1817. <li>The render tree doesn&rsquo;t <em>perfectly</em> parallel the DOM; it contains pseudo elements, shadow DOM, etc.</li>
  1818. </ul>
  1819. </li>
  1820. <li>100ms total render time feels &ldquo;instant&rdquo; to a user.</li>
  1821. <li>Layout thrashing is caused by querying/reading style attributes inside a loop that also changes style attributes.</li>
  1822. <li>To prevent layout thrashing, query/read starting values outside loops.</li>
  1823. <li>Scrolling isn&rsquo;t necessarily expensive from a painting perspective; it just moves the viewport around what has already been painted.</li>
  1824. <li>Fixed background images cause expensive repaints when scrolling—avoid them! Instead, use a background image that scrolls with the content to avoid repaints. (That may change since it depends on the browser implementation.)</li>
  1825. <li>On mobile, native <code>click</code> events have a 300ms delay since the browser waits to confirm whether the user is single- or double-tapping. Can work around this by:
  1826. <ul>
  1827. <li>Using <code>touchstart</code>/<code>touchend</code> events, but that may have unintended side-effects, unintentionally triggering those events when scrolling</li>
  1828. <li>Using a fixed viewport, which causes some browsers to intelligently disable double-tap detection</li>
  1829. <li>Using the <a href="">fastclick</a> library</li>
  1830. </ul>
  1831. </li>
  1832. <li>For displays that refresh at 60 Hz, 16.67ms is the frame scheduling deadline.</li>
  1833. <li><code>setTimeout()</code> isn&rsquo;t accurate enough for animations (frame scheduling.)
  1834. <ul>
  1835. <li>Even with high frame rates, animations will appear jittery since the frames aren&rsquo;t in sync with the refresh rate.</li>
  1836. <li>Instead, use <code>requestAnimationFrame()</code>, which has great browser support.</li>
  1837. </ul>
  1838. </li>
  1839. <li>24 FPS content shown on a screen with a 60 Hz refresh rate causes 3:2 pulldown since every other frame is extended to three refreshes. (For 50 Hz refresh rate, 24 FPS video is shown at 25 FPS; it&rsquo;s played slightly faster!)</li>
  1840. <li>Software rendering caused the old <a href="">&ldquo;IE error effect&rdquo;</a>. Modern operating systems use hardware rendering.</li>
  1841. <li>Let the browser use hardware rendering as often as possible:
  1842. <ul>
  1843. <li>For the time being, use CSS 3D transform hacks where appropriate, but beware of the side effects, like hitting the GPU memory barrier on mobile.</li>
  1844. <li>For CSS, animate using transforms instead of <code>left</code>/<code>top</code>.</li>
  1845. <li>Animations using <code>left</code>/<code>top</code> look jittery since they snap to the pixel grid; transforms don&rsquo;t snap to the pixel grid.</li>
  1846. <li>There are no magic rules around transforms and layering.</li>
  1847. <li>Don&rsquo;t trust performance tips, test everything yourself!</li>
  1848. </ul>
  1849. </li>
  1850. <li>Things that trigger new hardware rendering layers:
  1851. <ul>
  1852. <li>3D transforms</li>
  1853. <li>Animation/transforms/opacity/filters</li>
  1854. <li>Flash/Silverlight</li>
  1855. <li>Canvas</li>
  1856. <li>Video</li>
  1857. <li>Fixed position elements (sometimes)</li>
  1858. <li>Fixed backgrounds (soon!)</li>
  1859. <li>Anything on top of a layer</li>
  1860. </ul>
  1861. </li>
  1862. </ul>
  1863. <hr>
  1864. <h2 id="kevin-m-hoffman---designing-meetings-to-work-for-design-kevinmhoffmancomhttpwwwkevinmhoffmancom-bull-kevinmhoffmanhttpstwittercomkevinmhoffman">Kevin M. Hoffman - Designing Meetings to Work for Design (<a href=""></a> • <a href="">@kevinmhoffman</a>)</h2>
  1865. <ul>
  1866. <li>How do we collaborate better?</li>
  1867. <li><a href="">Marshmallow Challenge</a> team-building exercise: Of all age groups, Kindergartners are best at it because they spend most of their time <strong>doing</strong> rather than <strong>thinking</strong>.</li>
  1868. <li>Don&rsquo;t be afraid to fail.</li>
  1869. <li>Rapidly iterate.</li>
  1870. <li>Don&rsquo;t plan, don&rsquo;t discuss: just build (rapid prototyping).</li>
  1871. <li>What&rsquo;s better than hearing and seeing is discussing; a good meeting is an active discussion.</li>
  1872. <li>Your ability to retain the most information is when you&rsquo;re making and managing something.</li>
  1873. <li><strong>Doing</strong> is better than <strong>seeing</strong>, which is better than <strong>hearing</strong>.</li>
  1874. <li>&ldquo;If you&rsquo;re not prepared to be wrong, you&rsquo;ll never come up with anything original.&rdquo; —Sir Ken Robinson</li>
  1875. <li>Be wrong at the right time. Allow for failure in design meetings; that&rsquo;s much better than failing after you ship!</li>
  1876. </ul>
  1877. <h3 id="4-frameworks-for-better-design-meetings">4 frameworks for better design meetings</h3>
  1878. <ol>
  1879. <li>Always diverge before you try to converge.
  1880. <ul>
  1881. <li>Start the meeting with an opportunity for the discussion to expand, then arrive at a decision at the end.</li>
  1882. </ul>
  1883. </li>
  1884. <li>OARR: Outcomes, Agenda, Rules, Roles (David Sibbett)
  1885. <ul>
  1886. <li>Employ the four roles that make meetings productive:
  1887. <ul>
  1888. <li><strong>Facilitator</strong>: Neutral, doesn&rsquo;t evaluate or contribute ideas, just manages the meeting.</li>
  1889. <li><strong>Recorder</strong>: Creates group memory, records publicly, like on a whiteboard, is silent, and follows up afterwards.</li>
  1890. <li><strong>Group member</strong>: Contributes ideas, stays positive, isn&rsquo;t defensive, checks/balances other members and the facilitator.</li>
  1891. <li><strong>Leader</strong>: Designs the meeting, selects attendees and roles, decides upon goals, <strong>and becomes a group member during the meeting</strong>.</li>
  1892. </ul>
  1893. </li>
  1894. <li>If you&rsquo;re not in charge of the meeting, the biggest way to affect it is public recording. Volunteer to do it, you&rsquo;ll help everyone in the room to be more productive and cut down on repeating themselves.</li>
  1895. <li>Distribute/take turns in each role so everyone gets an equal opportunity to contribute.</li>
  1896. <li>For small meetings, there&rsquo;s no need for all roles, but someone should still serve as a facilitator/recorder.</li>
  1897. <li>3 questions of design: What has to stay the same? What can be changed? What can be eliminated?</li>
  1898. <li>Instead of discussing, have everyone write their feedback on color-coded, groupable stickies; you end up creating user requirements/user stories just by virtue of going through that process.</li>
  1899. </ul>
  1900. </li>
  1901. <li>Visual listening (via sketching) improves discussion and adds context.
  1902. <ul>
  1903. <li>Visual memory and recall are powerful.</li>
  1904. <li>Live-sketching a meeting could be useful; if you&rsquo;re less artistically inclined, sketching your thoughts beforehand is also useful.</li>
  1905. </ul>
  1906. </li>
  1907. <li>Present and design ideas collaboratively.
  1908. <ul>
  1909. <li>Do actual work in the meeting, don&rsquo;t just talk about work.</li>
  1910. <li>Example: When presenting personas, use something familiar like television characters rather than &ldquo;generic&rdquo; personas.</li>
  1911. <li>Example: For designing responsive content strategy, label every piece of content on the page. Split the content into groups, and let teams of people rate the priority of the cards inside each group. That way you have a mix of perspectives ranking the importance of a distributed variety of content elements.</li>
  1912. <li>Example: For designing interfaces, have small cross-disciplinary groups sketch as many concepts as they can. Then have groups repeatedly combine into larger groups and iterate on the design.</li>
  1913. </ul>
  1914. </li>
  1915. </ol>
  1916. <hr>
  1917. <h2 id="luke-wroblewski---its-a-writeread-mobile-web-lukewcomhttpwwwlukewcom-bull-lukewhttpstwittercomlukew">Luke Wroblewski - It&rsquo;s a Write/Read (Mobile) Web (<a href=""></a> • <a href="">@lukew</a>)</h2>
  1918. <ul>
  1919. <li>The 5 most popular web sites in the U.S.—Facebook, Yahoo, AIM, Google, and YouTube—are all write/read experiences; they don&rsquo;t work unless people add (write) content to them.</li>
  1920. <li>All of those sites are now moving to mobile.</li>
  1921. <li>&ldquo;The mobile moment&rdquo;: When the amount of your mobile users becomes larger than the number of your non-mobile users.</li>
  1922. <li>It&rsquo;s a myth that mobile devices aren&rsquo;t used for creating content. In 2011, 40% of tweets were created on mobile, and 3 hours of video per second were uploaded to YouTube via mobile.</li>
  1923. </ul>
  1924. <h3 id="how-do-we-design-for-mobile-creation">How do we design for mobile creation?</h3>
  1925. <h4 id="one-handed-use">One-handed Use</h4>
  1926. <ul>
  1927. <li>Test with one thumb!</li>
  1928. <li>iOS 7 will have improved gestures for single-thumb use.</li>
  1929. <li>&ldquo;What we need to do to design is to look at <strong>the extremes</strong>. The middle will take care of itself.&rdquo; —Dan Formosa</li>
  1930. <li>Think about how the keyboard can be avoided at all costs. Don&rsquo;t let the keyboard appear unless there&rsquo;s no other way.
  1931. <ul>
  1932. <li>Use smart defaults and suggestions to avoid making the user type manually.</li>
  1933. <li>Let people type manually if they really want to.</li>
  1934. </ul>
  1935. </li>
  1936. </ul>
  1937. <h4 id="visually-engaging">Visually Engaging</h4>
  1938. <ul>
  1939. <li>Images rule on mobile (and not just in social apps!)</li>
  1940. <li>Images are one of the best mediums for communication on mobile.</li>
  1941. <li>Imagery has a huge impact in commerce (eBay, hotel booking, etc.)</li>
  1942. <li>Performance is still important: We should work hard to keep things visually engaging without impacting performance.</li>
  1943. </ul>
  1944. <h4 id="focused-flows">Focused Flows</h4>
  1945. <ul>
  1946. <li>The user should have to do as little work as possible to accomplish a core task (Examples: Foursquare check-in, booking a hotel, etc.)</li>
  1947. <li>&ldquo;Creativity is people who care enough to keep thinking about something until they find the simplest way to do it.&rdquo; —Tim Cook</li>
  1948. <li>&ldquo;Booking a hotel happens in 3 taps and a swipe. This is a competitive advantage.&rdquo; —Sam Shank, CEO of HotelTonight</li>
  1949. <li>It takes big changes to go small.</li>
  1950. <li>Yelp doesn&rsquo;t allow users to write reviews from mobile since they view their users through the lens of the desktop; they&rsquo;re worried users will write reviews using &ldquo;SMS writing&rdquo;.</li>
  1951. <li>HotelTonight allows users to write reviews using photos rather than typing them out.</li>
  1952. <li>If you&rsquo;re making a lot of people uncomfortable with a big design decision, you&rsquo;re probably on the right track.</li>
  1953. </ul>
  1954. <h4 id="just-in-time-actions">Just-In-Time Actions</h4>
  1955. <ul>
  1956. <li>&ldquo;Intro tours&rdquo; aren&rsquo;t the best way to communicate how to create/make things in mobile apps. Instead, teach people in context using just-in-time education.</li>
  1957. <li>Show help or relevant actions when they&rsquo;re needed rather than bombarding the user with all possible actions at once.</li>
  1958. <li>Example: When and if you&rsquo;ve recently taken photos, the Google+ app shows recent photos for easy posting.</li>
  1959. <li>Example: When you start scrolling down in the Google+ app, the navigation bar jumps out of the way (but come back when you start scrolling back up.)</li>
  1960. </ul>
  1961. <h4 id="cross-device-usage">Cross Device Usage</h4>
  1962. <ul>
  1963. <li>Multiple devices can be used together for a cohesive input experience.</li>
  1964. <li><strong>Access</strong>: Native apps vs. mobile web apps? They&rsquo;re not necessarily opposites; use both at the same time. They can play off each other&rsquo;s strengths.</li>
  1965. <li><strong>Flow</strong>: Allows a process to travel across screens. (Example: Google Maps iOS and web apps share recently-entered data, eBay allows you to start creating a listing on one device and complete it on another.)</li>
  1966. <li><strong>Control</strong>: One device can control another. (Example: <a href="">OneID</a>)</li>
  1967. <li><strong>Push</strong>: One device sending something to a different device. (Example: eBay allows users to add a photo from a mobile device when creating a listing using the desktop web site.)</li>
  1968. </ul>
  1969. <hr>
  1970. <h2 id="jason-grigsby---the-immobile-web-userfirstwebcomhttpuserfirstwebcom-bull-grigshttpstwittercomgrigs">Jason Grigsby - The Immobile Web (<a href=""></a> • <a href="">@grigs</a>)</h2>
  1971. <ul>
  1972. <li>Televisions are the next wave in the &ldquo;device zombie apocalypse.&rdquo;</li>
  1973. <li>Televisions allow for cohesive experiences while using mobile devices. (Example: Game of Thrones shows extra info on SmartGlass.)</li>
  1974. <li>Big opportunity: An App Store on Apple TV.</li>
  1975. <li>The browsers built in to the newest televisions are actually surprisingly good; they pass HTML5/CSS3 tests.</li>
  1976. <li>The user experience of browsing the web on televisions is horrible; the biggest problem is input.</li>
  1977. <li>Two main methods of input for smart TVs: D-pads and pointers.
  1978. <ul>
  1979. <li>D-pads work very well when done properly. D-pads should not be used to control cursors.</li>
  1980. <li>Pointers work well with cursors, but precision is difficult.</li>
  1981. </ul>
  1982. </li>
  1983. <li>Gesture controls currently don&rsquo;t work very well.</li>
  1984. <li>Remote control design is still evolving (touch areas, etc.)</li>
  1985. <li>Context is irrelevant for mobile users since we can&rsquo;t know what it is, but context is becoming relevant for television.</li>
  1986. <li>Designs for 10-foot UIs should be task-oriented.</li>
  1987. <li>Hover is dead for mobile devices, but is back on TVs (for cursor input.)</li>
  1988. <li>Arbitrary <a href="">CSS</a> or JavaScript is still necessary to aid with input on televisions.</li>
  1989. <li>Televisions have inconsistent resolutions and overscan.</li>
  1990. <li>We need to put pressure on television browser makers to interoperate.</li>
  1991. <li>We still need to rely on device detection for the time being.</li>
  1992. <li>You can test designs on mobile devices at cell phone carrier stores, but can&rsquo;t do the same for smart TVs since none of them have remotes or a wi-fi connection at stores.</li>
  1993. <li>What are people actually expecting when they buy a smart TV?
  1994. <ul>
  1995. <li>Storage capacity and processor speed aren&rsquo;t listed as specs.</li>
  1996. <li>Do most people just want built-in Netflix?</li>
  1997. </ul>
  1998. </li>
  1999. <li>Are televisions the equivalent of cell phones before the iPhone?</li>
  2000. <li>Smart TVs suck right now, but it would be dangerous to dismiss them.</li>
  2001. <li>We can&rsquo;t predict future behavior from a current experience that sucks.</li>
  2002. </ul>
  2003. <hr>
  2004. <h2 id="ethan-marcotte---the-map--the-territory-ethanmarcottecomhttpethanmarcottecom-bull-beephttpstwittercombeep">Ethan Marcotte - The Map &amp; The Territory (<a href=""></a> • <a href="">@beep</a>)</h2>
  2005. <ul>
  2006. <li>Responsive designs use a fluid grid, flexible images, and media queries.</li>
  2007. <li>Converting a fixed grid to a fluid grid: target ÷ context = result</li>
  2008. <li>Media queries are sized to arbitrary <code>em</code> units based on readability, <em>not</em> screen/device measurements.</li>
  2009. <li>Across different resolutions (media queries), you can re-use the same navigational elements by repositioning them using absolute positioning. (Example: An element that is shown inside a submenu at small sizes can be repositioned into the main masthead at larger sizes. The basic functionality and markup don&rsquo;t change between display sizes.)</li>
  2010. <li>Average page weight was 320 KB in 2009, and 1.4 MB in 2013. Over four years, average page weight has increased 400%.</li>
  2011. <li>&ldquo;The more accurate the map, the more it resembles the territory. The most accurate map possible would be the territory, and thus would be perfectly accurate and perfectly useless.&rdquo; —Neil Gaiman, <em>American Gods</em></li>
  2012. <li>7 billion mobile subscriptions in 2013, 60% are on EDGE/CDMA.</li>
  2013. <li>Sustainability in web design:
  2014. <ul>
  2015. <li><strong>Reduce</strong>: Reducing page weight can open your site to new markets. Use the <a href="">smallest possible JavaScript libraries</a>.</li>
  2016. <li><strong>Revisit</strong>: Revisit some of our old assumptions about design. The web is a new medium that needs a new aesthetic.</li>
  2017. </ul>
  2018. </li>
  2019. <li>&ldquo;&lsquo;We don&rsquo;t have any non-JavaScript users&rsquo; No, all your users are non-JS while they&rsquo;re downloading your JS&rdquo; —<a href="">Jake Archibald</a></li>
  2020. <li>&ldquo;What works good is better than what looks good, because what works good lasts.&rdquo; —Ray Eames</li>
  2021. </ul>
  2022. <hr>
  2023. <h1 id="day-2-62513">Day 2: 6/25/13</h1>
  2024. <h2 id="karen-mcgrane---the-mobile-content-mandate-karenmcgranecomhttpkarenmcgranecom-bull-karenmcgranehttpstwittercomkarenmcgrane">Karen McGrane - The Mobile Content Mandate (<a href=""></a> • <a href="">@karenmcgrane</a>)</h2>
  2025. <ul>
  2026. <li>&ldquo;There is no reason for any individual to have a computer in his home.&rdquo; —Ken Olsen, CEO of Digital Equipment Corporation</li>
  2027. <li>&ldquo;There is no reason anyone will need to do that on mobile.&rdquo; —Your company, probably</li>
  2028. <li>How could cheap PCs compete with minicomputers from DEC, the world&rsquo;s second largest computer company in 1988?</li>
  2029. </ul>
  2030. <h3 id="disruptive-innovation">Disruptive Innovation</h3>
  2031. <blockquote>
  2032. <p>In industry after industry&hellip;the new technologies that had brought the big, established companies to their knees weren&rsquo;t better or more advanced—they were actually worse. The new products were low-end, dumb, shoddy, and in almost every way inferior. But the new products were usually cheaper and easier to use, and so people or companies who were not rich or sophisticated enough for the old ones started buying the new ones, and there were so many more of the regular people than there were of the rich, sophisticated people that the companies making the new products prospered.</p>
  2033. </blockquote>
  2034. <p>—<a href="">The New Yorker, <em>When Giants Fail</em></a></p>
  2035. <ul>
  2036. <li>Examples:
  2037. <ul>
  2038. <li>Handcrafted, high-quality 1940s cabinet radios were replaced by cheaper, lower quality portable transistor radios.</li>
  2039. <li>Offset printers were replaced by cheap inkjet printers.</li>
  2040. <li>People predicted that digital cameras would disrupt the film industry, but nobody predicted that digital cameras would disrupt the entire camera industry (cameraphones, etc.)</li>
  2041. </ul>
  2042. </li>
  2043. <li>We&rsquo;re currently experiencing the next great wave of computing.</li>
  2044. <li>Mobile devices are becoming a personal computing device for people who have never had access to the Internet before.</li>
  2045. <li>The iPhone was originally seen as a luxury, high-end cell phone as opposed to a really cheap computer.</li>
  2046. </ul>
  2047. <h3 id="the-mobile-only-user">The Mobile-Only User</h3>
  2048. <ul>
  2049. <li>Mobile phones and smartphones <strong>are not</strong> two different segments of the market, just like there weren&rsquo;t two markets for color vs. black-and-white televisions.</li>
  2050. <li>Lots of minority groups don&rsquo;t have access to the Internet or broadband at home, but nearly everyone has a phone.</li>
  2051. <li>Lots of minority groups <strong>only</strong> (or mostly) use the Internet on mobile.</li>
  2052. <li>&ldquo;Mobile-optimized&rdquo; sites usually have a paltry subset of the content of the &ldquo;full desktop&rdquo; version. This crutch has gotten us through the last five years of mobile adoption, but <strong>this isn&rsquo;t good enough.</strong></li>
  2053. <li>We can&rsquo;t force users to pinch-and-zoom their way around desktop sites on a mobile device. (&ldquo;It&rsquo;s like reading a newspaper through a toilet paper tube.&quot;)</li>
  2054. <li>Mobile users are being treated as second-class citizens since web designers expect that people will use the &ldquo;real web site&rdquo; on a desktop PC.</li>
  2055. </ul>
  2056. <h3 id="content-strategy-for-mobile">Content Strategy for Mobile</h3>
  2057. <h4 id="know-your-workflow">Know Your Workflow</h4>
  2058. <ul>
  2059. <li>There shouldn&rsquo;t be separate &ldquo;mobile&rdquo; and &ldquo;web&rdquo; content teams.</li>
  2060. <li>Don&rsquo;t fork your content for mobile: You would have to maintain and update two independent but similar pieces of content.</li>
  2061. <li>Being forced to be succinct sometimes makes existing mobile web sites better and easier to read than their desktop counterparts. If the mobile site is better, why isn&rsquo;t it the site for everyone?</li>
  2062. <li>There&rsquo;s no such thing as &ldquo;how to write for mobile&rdquo;; there&rsquo;s just good writing!</li>
  2063. <li>Good content transcends platform. If you have interesting, well-written, appropriately structured content, it will easily make the link to mobile. (Example: <a href="">American Cancer Society web site</a>.)</li>
  2064. </ul>
  2065. <h4 id="chunk-your-blobs">Chunk Your Blobs</h4>
  2066. <ul>
  2067. <li>Content shouldn&rsquo;t be specifically associated with any part of the layout of a web page.</li>
  2068. <li>Which content should be included or excluded?</li>
  2069. <li>Should longer pages be broken into shorter ones?</li>
  2070. <li>Will it work to reuse headings as links?</li>
  2071. <li>Will it work to truncate body copy for teasers? (Example: This doesn&rsquo;t work for Amazon&rsquo;s mobile site; the truncated body copy has no value since product names and specs are just repeated.</li>
  2072. <li>Responsive design won&rsquo;t fix your content problem.</li>
  2073. <li>The Daily Beast, NPR, and The Guardian truncate headlines rather than giving them proper real estate on mobile. (<a href=""></a>)</li>
  2074. <li>Either give headlines more real estate, or write shorter headlines.</li>
  2075. <li>Netflix is a great example of chunked content—it is available on hundreds of devices but they never truncate content; they show the appropriate amount of detail/content for a given platform.</li>
  2076. </ul>
  2077. <h3 id="in-conclusion">In Conclusion</h3>
  2078. <ul>
  2079. <li>Don&rsquo;t create content for a specific context.</li>
  2080. <li>You don&rsquo;t get to decide which device people use to access your content; they do.</li>
  2081. <li>Disruptive technologies eventually get good, or they redefine what good means.</li>
  2082. <li>Do mobile right, right from the start.</li>
  2083. </ul>
  2084. <hr>
  2085. <h2 id="eric-meyer---strong-layout-systems-meyerwebcomhttpmeyerwebcom-bull-meyerwebhttpstwittercommeyerweb">Eric Meyer - Strong Layout Systems (<a href=""></a> • <a href="">@meyerweb</a>)</h2>
  2086. <ul>
  2087. <li>When it started out, CSS was an appearance system, not a layout system.</li>
  2088. <li>CSS1 had floats, but they weren&rsquo;t meant to be used for layout. <code>clear</code> is the only reason we used floats for layout, otherwise we would have stuck with tables.</li>
  2089. <li>&ldquo;<code>clear</code> was a screwdriver we used to pound in a nail since no one had given us a hammer yet.&rdquo;</li>
  2090. <li>CSS2 added positioning, which helped slightly with layout. <a href=""></a> had a 3-column layout in 2002.</li>
  2091. <li>Design decisions were made in the context of the limitations of the technology.</li>
  2092. <li>We&rsquo;ve internalized the limitation that positioned/floated elements are only as tall as their content and that &ldquo;float drop&rdquo; can happen.</li>
  2093. <li>The old limitations of CSS have limited the scope of our perceived design choices/toolbox; unlearning these limitations and assumptions will become a vital skill.</li>
  2094. </ul>
  2095. <h3 id="viewport-units">Viewport Units</h3>
  2096. <ul>
  2097. <li><a href=""></a></li>
  2098. <li>Viewport units look similar to percentage units but they&rsquo;re not. Percentage elements size relative to their parent element while viewport elements size relative to the viewport.</li>
  2099. </ul>
  2100. <h3 id="flexbox">Flexbox</h3>
  2101. <ul>
  2102. <li><a href=""></a></li>
  2103. <li>Reminiscent of table layouts but much more powerful.</li>
  2104. <li><a href=""><code>justify-content</code></a> and <a href=""><code>flex-wrap</code></a> replace the need to do width/margin/wrapping calculations.</li>
  2105. <li>Allows you to mix units (two elements that are placed next to each other can have different units.) The space between them isn&rsquo;t margin or padding, it&rsquo;s just available space not yet &ldquo;eaten up&rdquo; by the flexbox algorithm.</li>
  2106. <li><code>display: flex</code> must be applied to the <strong>parent element</strong> of whatever elements you want to be flexible.</li>
  2107. <li>Flexible elements can be rearranged at will with <code>order</code>. Regardless of order, selectors (<code>:first-child</code>, <code>:last-child</code>, etc.) will still respect the DOM and ignore the flex flow.</li>
  2108. <li>There&rsquo;s nothing stopping an element that&rsquo;s flexible from also being the master context for its own flexible children.</li>
  2109. </ul>
  2110. <h3 id="grid-layout">Grid Layout</h3>
  2111. <ul>
  2112. <li><a href=""></a></li>
  2113. <li><a href="">Browser support isn&rsquo;t great yet</a>, since the standard is still being [re]written.</li>
  2114. <li>Grids can be nested, and mixed and matched with flexbox.</li>
  2115. <li>Simple syntax (but simple doesn&rsquo;t necessarily mean easy!)</li>
  2116. </ul>
  2117. <h3 id="regions-and-shapes">Regions and Shapes</h3>
  2118. <ul>
  2119. <li><a href=""></a>, <a href=""></a></li>
  2120. <li>Regions separate layout from content by allowing content to flow between elements.</li>
  2121. <li><strong>Not</strong> the web as we&rsquo;re used to it, but may become the web as we&rsquo;re used to it very soon.</li>
  2122. <li>Can combine regions and shapes to mimic complex print layouts.</li>
  2123. </ul>
  2124. <hr>
  2125. <h2 id="lea-verou---deep-css-secrets-veroumehttpveroume-bull-leaverouhttpstwittercomleaverou">Lea Verou - Deep CSS Secrets (<a href=""></a> • <a href="">@LeaVerou</a>)</h2>
  2126. <p><em>Interactive slides are available at <a href=""></a>.</em></p>
  2127. <h3 id="background-attachment-local"><code>background-attachment: local;</code></h3>
  2128. <ul>
  2129. <li>Background scrolls with the page <strong>and</strong> with the element.</li>
  2130. <li>Can be used to implement &ldquo;more content&rdquo; indicators inside scrollable areas à la Google Reader: can be applied to elements that block the &ldquo;more content&rdquo; indicators when scrolled to the top or bottom of a scrollable area.</li>
  2131. <li>Decent browser support (except Firefox).</li>
  2132. <li><a href=""></a></li>
  2133. </ul>
  2134. <h3 id="fixed-width-fluid-background">Fixed Width, Fluid Background</h3>
  2135. <ul>
  2136. <li>An effect where the background resizes but the content width is fixed.</li>
  2137. <li>You don&rsquo;t need wrapper elements and inner elements with margins, just use <code>padding</code> with <code>calc</code>.</li>
  2138. <li><a href="">Decent browser support for <code>calc</code></a> (except Opera).</li>
  2139. </ul>
  2140. <h3 id="lightboxes">Lightboxes</h3>
  2141. <ul>
  2142. <li>An effect where an image is displayed by expanding the width and then the height.</li>
  2143. <li>Combine independent <a href="">CSS transitions</a> for height and width, and add a delay the 2nd transition.</li>
  2144. <li>Can exploit the fact that the CSS <code>transition</code> property itself does not transition.</li>
  2145. <li><a href="">Decent browser support for CSS transitions</a>.</li>
  2146. </ul>
  2147. <h3 id="lined-paperzebra-striping-effect">Lined Paper/Zebra Striping Effect</h3>
  2148. <ul>
  2149. <li>Create a background by tiling a linear gradient. Space the tiling using the <code>line-height</code> of the text.</li>
  2150. <li>Can also make the background lines respect padding by using the <a href=""><code>background-origin</code> property</a> (<code>background-origin: content-box;</code>)</li>
  2151. <li>Can also use the same principles to zebra-stripe text, without needing wrapping elements for each stripe.</li>
  2152. <li><a href="">Decent browser support for <code>background-origin</code>.</a></li>
  2153. </ul>
  2154. <h3 id="diamond-outlined-images">Diamond-Outlined Images</h3>
  2155. <ul>
  2156. <li>Wrap an image with a wrapping element, rotate the wrapping element by 45 degrees, then rotate the image -45 degrees.</li>
  2157. <li>Rotation is achieved using CSS transforms.</li>
  2158. <li><a href="">Decent browser support for CSS transforms.</a></li>
  2159. </ul>
  2160. <h3 id="make-elements-trace-a-circular-path">Make Elements Trace a Circular Path</h3>
  2161. <ul>
  2162. <li>One solution: Make a wrapper element trace a circle using CSS animation and <code>transform-origin</code>, then counter-rotate the original element so it always faces the same direction while tracing a circular path (doesn&rsquo;t rotate in place.)</li>
  2163. <li>Optimize by reusing the same <code>@keyframes</code> for both animations, but reverse one animation with <a href=""><code>animation-direction</code></a>.</li>
  2164. <li>Multiple transforms layer on each other; transforms stack on top of any changes caused by the previous transforms.</li>
  2165. <li><a href="">Decent browser support for CSS animations.</a></li>
  2166. </ul>
  2167. <h3 id="non-boxy-shadows">Non-Boxy Shadows</h3>
  2168. <ul>
  2169. <li>Use <code>filter: drop-shadow</code> instead of <code>box-shadow</code> to draw shadows behind irregularly shaped elements (like speech bubbles).</li>
  2170. <li>Can use SVG filters for browsers that don&rsquo;t support CSS filters.</li>
  2171. <li><a href="">Poor browser support for CSS filters.</a></li>
  2172. </ul>
  2173. <h3 id="glass-pane-effect">Glass Pane Effect</h3>
  2174. <ul>
  2175. <li>Text written inside a &ldquo;glass pane&rdquo; element positioned over a background image is hard to read. How do we blur the background of the glass pane without blurring the text?</li>
  2176. <li>Add a <code>:before</code> pseudo-element to the glass pane, give it the same background image as the preexisting background image, and blur it using <code>filter: blur</code>.</li>
  2177. <li>Allows you to not need an alternate pre-blurred version of the background image.</li>
  2178. <li>Messy background positioning unfortunately still applies.</li>
  2179. <li>Degrades gracefully for browsers that don&rsquo;t support CSS filters—the image will just be transparent instead of blurred.</li>
  2180. </ul>
  2181. <h3 id="hyphens-property"><code>hyphens</code> Property</h3>
  2182. <ul>
  2183. <li><code>hyphens: auto;</code> makes justified text much more readable; eliminates ugly whitespace rivers.</li>
  2184. <li><a href="">Poor browser support for the <code>hyphens</code> property.</a></li>
  2185. </ul>
  2186. <h3 id="frame-animations">Frame Animations</h3>
  2187. <ul>
  2188. <li>An effect that achieves animation by manipulating the background position of an image that contains frames.</li>
  2189. <li>Use <code>steps</code> with CSS animations to do discrete easing rather than continuous easing. This shows each frame in succession instead of continuously sliding the background image.</li>
  2190. <li><a href=""></a></li>
  2191. <li><a href=""></a></li>
  2192. </ul>
  2193. <hr>
  2194. <h2 id="kim-goodwin---silo-busting-with-scenarios-kimgoodwinhttpstwittercomkimgoodwin">Kim Goodwin - Silo-Busting with Scenarios (<a href="">@kimgoodwin</a>)</h2>
  2195. <ul>
  2196. <li>Organizing teams by platform/geography/features limits those teams&rsquo; worldviews.</li>
  2197. <li>Example of an agile user story: &ldquo;As a user, I want to log in to access my account.&rdquo;
  2198. <ul>
  2199. <li>When has a real user said, &ldquo;Gee, I want to &lsquo;log in&rsquo;?&rdquo;</li>
  2200. </ul>
  2201. </li>
  2202. <li>We all fall victim to having siloed mindsets, even for low-level functionality.</li>
  2203. <li>A <strong>scenario</strong> is a plausible future story about a persona using the product or service from start to finish.</li>
  2204. <li>Scenarios involve and star human characters, not just roles (&ldquo;user&rdquo; or &ldquo;admin&rdquo; are just roles.) We&rsquo;re people, not roles.</li>
  2205. <li>Good process <strong>oscillates</strong> between generative (divergent) and analytical (convergent).</li>
  2206. <li>First rule of user research: Forget what you&rsquo;re building since that will make you think much too narrowly.</li>
  2207. <li>User research can clarify and expose information about the big picture and the problem you&rsquo;re trying to solve, rather than just what you&rsquo;re building.</li>
  2208. <li>Create a journey map—what frustrates the user during the entire process of achieving their own goals?</li>
  2209. <li>After that, what can we do to &ldquo;un-suckify&rdquo; the worst part(s) of the experience?</li>
  2210. <li>Just like you wouldn&rsquo;t call a good restaurant &ldquo;really edible&rdquo;, good usability isn&rsquo;t good enough—we have to go out of our way to delight users. &ldquo;Our job is to be delightfulness experts.&rdquo;</li>
  2211. <li>Add something unexpectedly good. What would a helpful human do?</li>
  2212. <li>Make it a story.</li>
  2213. <li>Once all of the information is collected, discuss and decide on priorities with stakeholders.</li>
  2214. <li>Look at your silo, informed by the bigger journey.</li>
  2215. <li>Use scenarios to guide rough storyboards: What&rsquo;s on the screen and how it&rsquo;s laid out. Don&rsquo;t stress about widgets and words.</li>
  2216. <li>Look for convergence between scenarios, but prioritize as you converge.</li>
  2217. <li>Scenarios drive site structure.</li>
  2218. <li>Polish the details.</li>
  2219. <li>Avoid UX purgatory.</li>
  2220. <li>Good experiences only happen when everyone who is responsible for part of the experience is invested in creating the whole experience.</li>
  2221. </ul>
  2222. <hr>
  2223. <h2 id="mike-monteiro---what-clients-dont-know-and-why-its-your-fault-mikemonteirocomhttpmikemonteirocom-bull-mike_ftwhttpstwittercommike_ftw">Mike Monteiro - What Clients Don&rsquo;t Know (and Why It&rsquo;s Your Fault) (<a href=""></a> • <a href="">@Mike_FTW</a>)</h2>
  2224. <ul>
  2225. <li>Designers: You are in the service industry! You have clients and they need your help.</li>
  2226. <li>We get irritated by having to explain what is second nature to us.</li>
  2227. <li>To those on the outside, the process of buying design is as mysterious as making it. It&rsquo;s all magic.</li>
  2228. <li>If you&rsquo;re a designer, you&rsquo;re in the confidence game.</li>
  2229. <li>Designers need to have empathy for clients.</li>
  2230. <li>Your job isn&rsquo;t just making things, that&rsquo;s the easy part! It&rsquo;s convincing people that the shit you thought up in the shower that morning is right.</li>
  2231. <li>If it helps you do your job, it&rsquo;s part of your job.</li>
  2232. <li>Don&rsquo;t work with anyone you can&rsquo;t respect, since you won&rsquo;t be able to empathize with them.</li>
  2233. <li>Put yourself in your clients&rsquo; less stylish shoes.</li>
  2234. <li>You can&rsquo;t change how others behave, but you can change how you behave and react to a situation to meet a common goal.</li>
  2235. <li>Clients don&rsquo;t know when to get a designer involved.</li>
  2236. <li>&ldquo;&lsquo;Creative&rsquo; is a hate word. My mother raised three kids on a seamstress&rsquo;s salary—THAT&rsquo;S creative.&rdquo;</li>
  2237. <li>&ldquo;As long as you act like a disenfranchised &lsquo;creative,&rsquo; that&rsquo;s how you deserve to be treated.&rdquo;</li>
  2238. <li>Eye rolling is not a design skill.</li>
  2239. <li>Complaining is not a design skill.</li>
  2240. <li>&ldquo;They never asked me&rdquo; is not a design skill.</li>
  2241. <li>Stop waiting for an invitation to do your job—assert yourself.</li>
  2242. <li>Clients don&rsquo;t know the best way to evaluate a designer.</li>
  2243. <li>Clients don&rsquo;t know how to read your portfolio—the work <strong>does not</strong> speak for itself.</li>
  2244. <li>Retail suit store: &ldquo;Don&rsquo;t sell the suit, sell the service.&rdquo;</li>
  2245. <li>&ldquo;Sell [clients] the services you provide, using your sites as props.&rdquo;</li>
  2246. <li>Be upfront and let clients know if you&rsquo;re not the right person for the job.</li>
  2247. <li>Referrals are awesome—if you get a referral, it means you&rsquo;re not an asshole. Nobody is going to put someone they know in the hands of an asshole.</li>
  2248. <li>Every job you do is a sales pitch for the next job.</li>
  2249. <li>RFPs may be a client&rsquo;s way to tell you that they&rsquo;re scared.</li>
  2250. <li>On fighting with clients about RFPs: &ldquo;As long as we keep doing it, no one is going to stop expecting it.&rdquo;</li>
  2251. <li>Pick up the phone.</li>
  2252. <li>Learn to say <strong>no</strong>.</li>
  2253. <li>Learn to ask <strong>why</strong>.</li>
  2254. <li>Learn to say <strong>I don&rsquo;t know</strong>.</li>
  2255. <li>Clients want reassurance that they&rsquo;ll be in good hands with you, so they ask for the one thing they&rsquo;re familiar with—the outcome! &ldquo;Let&rsquo;s have them do comps!&rdquo;</li>
  2256. <li>As a designer, it&rsquo;s your job to walk them back from that conclusion and figure out the issue they&rsquo;re trying to solve.</li>
  2257. <li>&ldquo;The process you have that gets you from one point to another is only as good as your willingness to stand up for it.&rdquo;</li>
  2258. <li>&ldquo;Show the client they&rsquo;re in good hands, not by reacting to their request, but by addressing the fear behind that request.&rdquo;</li>
  2259. <li>&ldquo;Never work for someone you can&rsquo;t argue with. Show clients you&rsquo;re not going to let anyone mess up the process, even them.&rdquo;</li>
  2260. <li>Clients don&rsquo;t know why things cost what they do.</li>
  2261. <li>Design is a solution to a problem within a set of constraints.</li>
  2262. <li>&ldquo;Your budget is one of the most important constraints there is. Don&rsquo;t make it a secret, make it a data point.&rdquo;</li>
  2263. <li>Clients don&rsquo;t know what the process looks like.</li>
  2264. <li>Your process is a mystery. Clients don&rsquo;t want to think about it.</li>
  2265. <li>Clients deal with the unknown by applying their own process, which is comfortable and familiar to them.</li>
  2266. <li>Do everything in your power to be right, but never be afraid to be wrong.</li>
  2267. <li>Letting a client tell you how to do your job is stupid. &ldquo;Nature abhors a vacuum. So do clients. They will fill it.&rdquo;</li>
  2268. <li>It&rsquo;s not their job—it&rsquo;s yours!</li>
  2269. <li>Never, ever, ever throw another designer under the bus to advance your own agenda. (&ldquo;You should clap for that!&quot;)</li>
  2270. <li>No one is born a good client, just like no one is born a good designer.</li>
  2271. <li>A doctor wouldn&rsquo;t be able to have a conversation with you about an ailment on par with how he would converse about it with another doctor.</li>
  2272. <li>&ldquo;Please take all my clients from me.&rdquo;</li>
  2273. <li>You are a terrible mind reader.</li>
  2274. <li>&ldquo;&lsquo;Hope&rsquo; is not a design word. &lsquo;Empathy&rsquo; is.&rdquo;</li>
  2275. <li>The way to become a better designer is to help clients become better clients.</li>
  2276. <li>You are not a pixelpusher.</li>
  2277. <li>You are responsible for what you bring into the world.</li>
  2278. <li>Everything that&rsquo;s wrong with design today is your fault—and that is good news!</li>
  2279. <li>Working together with mutual respect can fix any problem you set your mind to.</li>
  2280. </ul>
  2281. <hr>
  2282. <h2 id="jared-spool---its-a-great-time-to-be-a-ux-designer-uiecomhttpuiecom-bull-jmspoolhttpstwittercomjmspool">Jared Spool - It&rsquo;s a Great Time To Be a UX Designer (<a href=""></a> • <a href="">@jmspool</a>)</h2>
  2283. <ul>
  2284. <li>Design is the rendering of intent.</li>
  2285. <li>Intention falls on a scale that spans from imitation to innovation (and corresponding expense, risk, and value.)</li>
  2286. <li>Business wins when it is intentionally innovative, and when it values designers.</li>
  2287. <li>Example: Airbnb ousted Craigslist for vacation rentals, which itself ousted newspaper classified ads.</li>
  2288. <li>Design is no longer about the visual; it&rsquo;s about the business.</li>
  2289. <li>Great business models are intentionally designed. (Example: Apple&rsquo;s end-to-end manufacturing, distribution, and sales.)</li>
  2290. <li>&ldquo;The largest room in the world is the room for improvement.&rdquo;</li>
  2291. <li>On Apple: &ldquo;How cool would it be to have &lsquo;Genius&rsquo; on your business card? That would totally change Thanksgiving.&rdquo;</li>
  2292. <li>Innovation is not adding new invention; innovation is adding new value.</li>
  2293. <li>Experiences can be mapped, measured, and designed. What do we intend?</li>
  2294. <li>Experience design: The rendering of intent within the gaps. (Example: <a href="">GE Adventure Series</a>)</li>
  2295. <li>Old Chinese proverb: Be careful what you ask for, lest it become so.</li>
  2296. <li>The best designers are good at storytelling, critiquing, sketching, presenting, and facilitating.</li>
  2297. <li>Specialists have more expertise in one area over others, generalists have equal expertise in most areas. Compartmentalists have expertise in a single area.</li>
  2298. <li>Teams need generalists more than specialists. Compartmentalists are the least valuable—being a compartmentalist is a career-limiting decision.</li>
  2299. <li>Experience designer: also known as a unicorn. (People don&rsquo;t believe they exist.)</li>
  2300. <li>How do you make a unicorn?
  2301. <ol>
  2302. <li>Train yourself</li>
  2303. <li>Practice your skills</li>
  2304. <li>Deconstruct as many designs as you can</li>
  2305. <li>Seek out feedback (and listen to it)</li>
  2306. <li>Teach others (you learn something when you teach something)</li>
  2307. </ol>
  2308. </li>
  2309. <li>The unicorn is design&rsquo;s most important innovation.</li>
  2310. </ul>
  2311. <hr>
  2312. <h1 id="conclusion">Conclusion</h1>
  2313. <p>Interestingly, my takeaways are almost identical to last year&rsquo;s (mobile, mobile, mobile!):</p>
  2314. <ul>
  2315. <li>Design a single experience that works well on mobile <strong>and</strong> on the desktop (mobile-first, responsive.)</li>
  2316. <li>Let mobile be the measuring stick for your content—if you don&rsquo;t need it on mobile, do you need it at all?</li>
  2317. <li>Since mobile and desktop should be a single experience, they should have complete content and feature parity.</li>
  2318. <li>Performance (speed and data usage) is important, especially on mobile.</li>
  2319. </ul>
  2320. <p>As a bonus, I also concluded that bacon cupcakes actually exist, and are in fact delicious:</p>
  2321. <p><img src="/post_assets/2013/06/aea_boston_2013_bacon_cupcake.jpg" alt="Bacon Cupcake"></p>
  2322. <p>Just like last year, An Event Apart was extremely well-organized, informative and inspirational, and I&rsquo;m very glad that I was able to attend!</p>
  2323. ]]>
  2324.    </content>
  2325.  </entry><entry>
  2326.    <title>Sleep Displays with Alfred v2</title>
  2327.    <link rel="alternate" type="text/html" href="" />
  2328.    <id>,2013:/2013/02/27/sleep_displays_with_alfred_v2.html</id>
  2329.    <published>2013-02-27T00:00:00-05:00</published>
  2330.    <updated>2013-02-27T00:00:00-05:00</updated>
  2331.    <author>
  2332.      <name>Josh Dick</name>
  2333.      <uri></uri>
  2334.    </author>
  2335.    <content type="html" xml:lang="en">
  2336.        <![CDATA[<blockquote>Because my keyboard doesn&rsquo;t have an eject key.</blockquote><h2 id="introduction">Introduction</h2>
  2337. <p>I can&rsquo;t use a Mac for more than a few minutes without somehow interacting with <a href="">Alfred</a>. I use an excellent Alfred extension by <a href="">Tony Wang</a> called <a href="">Sleep Display</a>. When triggered via a hotkey, the extension powers off all connected displays without actually suspending/sleeping the computer. While it&rsquo;s true that simultaneously pressing Control+Shift+Eject also accomplishes the same thing, the extension is useful for those whose keyboards don&rsquo;t have an eject key.</p>
  2338. <p>The first public beta of the next version of Alfred, Alfred v2, <a href="">became available</a> a few weeks ago. Since v2 has done away with extensions and has replaced them with a feature called &ldquo;Workflows&rdquo;, Tony&rsquo;s extension isn&rsquo;t compatible with v2. Further, v2 doesn&rsquo;t natively support shutting off displays as a built-in &ldquo;System Command&rdquo; when building Workflows (yet!).</p>
  2339. <p>To fill the gap, I decided to create a v2 Workflow called &ldquo;Sleep Displays&rdquo;. (Yes, I added an &ldquo;s&rdquo; to the the name of Tony&rsquo;s original extension. Yes, I&rsquo;m creative.)</p>
  2340. <h2 id="how-it-works">How It Works</h2>
  2341. <p>The Workflow contains a binary program, directly lifted from Tony&rsquo;s extension, that was built using the following code found <a href="">at Stack Overflow</a>:</p>
  2342. <div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-c" data-lang="c"><span style="color:#75715e">#include</span> <span style="color:#75715e">&lt;CoreFoundation/CoreFoundation.h&gt;</span><span style="color:#75715e">
  2343. </span><span style="color:#75715e">#include</span> <span style="color:#75715e">&lt;IOKit/IOKitLib.h&gt;</span><span style="color:#75715e">
  2344. </span><span style="color:#75715e"></span>
  2345. <span style="color:#75715e">/* Returns 0 on success and 1 on failure. */</span>
  2346. <span style="color:#66d9ef">int</span> <span style="color:#a6e22e">display_sleep</span>(<span style="color:#66d9ef">void</span>)
  2347. {
  2348.    io_registry_entry_t reg <span style="color:#f92672">=</span> IORegistryEntryFromPath(kIOMasterPortDefault, <span style="color:#e6db74">&#34;IOService:/IOResources/IODisplayWrangler&#34;</span>);
  2349.    <span style="color:#66d9ef">if</span> (reg) {
  2350.                IORegistryEntrySetCFProperty(reg, CFSTR(<span style="color:#e6db74">&#34;IORequestIdle&#34;</span>), kCFBooleanTrue);
  2351.                IOObjectRelease(reg);
  2352.        } <span style="color:#66d9ef">else</span> {
  2353.                <span style="color:#66d9ef">return</span> <span style="color:#ae81ff">1</span>;
  2354.        }
  2355.        <span style="color:#66d9ef">return</span> <span style="color:#ae81ff">0</span>;
  2356. }
  2357. </code></pre></div><p>According to the Stack Overflow answer, the code can be compiled on Mac with <code>gcc</code> using the flags <code>-framework CoreFoundation -framework IOKIT</code>.</p>
  2358. <h2 id="can-i-download-it-already">Can I Download It Already?</h2>
  2359. <p>You sure can. <a href="/post_assets/2013/02/Sleep%20Displays.alfredworkflow">Grab it right here.</a></p>
  2360. <h2 id="thats-all-folks">That&rsquo;s All, Folks</h2>
  2361. <p>Lacking the ability to sleep displays via a hotkey was the last thing preventing me from using Alfred v2 full time. Now I can do that with v2, and so can you.</p>
  2362. ]]>
  2363.    </content>
  2364.  </entry><entry>
  2365.    <title>My Git Prompt for Zsh</title>
  2366.    <link rel="alternate" type="text/html" href="" />
  2367.    <id>,2012:/2012/12/30/my_git_prompt_for_zsh.html</id>
  2368.    <published>2012-12-30T00:00:00-05:00</published>
  2369.    <updated>2012-12-30T00:00:00-05:00</updated>
  2370.    <author>
  2371.      <name>Josh Dick</name>
  2372.      <uri></uri>
  2373.    </author>
  2374.    <content type="html" xml:lang="en">
  2375.        <![CDATA[<blockquote>Because <!-- raw HTML omitted -->git status<!-- raw HTML omitted --> isn&rsquo;t nearly as fun.</blockquote><blockquote>
  2376. <p><em><strong>Update on June 8, 2017:</strong> After using this Git prompt for about 4½ years, I&rsquo;ve made <a href="/2017/06/08/my_git_prompt_for_zsh_revisited.html">some minor tweaks</a> to it.</em></p>
  2377. <p><em><strong>Update on January 8, 2013:</strong> The Git prompt code was missing some initialization options that were local to my <code>zsh</code> configuration file (<code>.zshrc</code>). I&rsquo;ve updated the code to include the necessary options.</em></p>
  2378. </blockquote>
  2379. <p>It has become rare for me to use a computer for longer than a few hours without using <a href="">Git</a>.</p>
  2380. <p>Although <a href="">many</a> <a href="">great</a> <a href="">tools</a> are available for graphically interacting with Git, I use Git almost exclusively on the command line, since that&rsquo;s how and where I first <a href="">learned to use Git</a>. (I believe it would be beneficial for anyone trying to learn Git to learn on the command line; doing so exposes Git&rsquo;s methodology in a <a href="">fundamental way</a> that promotes understanding, but that&rsquo;s a topic for another post.)</p>
  2381. <p>Any time I find an opportunity to offset development workflow friction from myself to the computer, I jump on it. In that vein, in order to save time and <a href="">be lazier</a> when working with Git, I&rsquo;ve pieced together a helpful <a href="">shell</a> prompt that conveys lots of information about a Git repository at a glance. The prompt works with <a href=""><code>zsh</code></a>, my shell of choice.</p>
  2382. <p>There are many examples of custom &ldquo;SCM-enabled&rdquo; shell prompts across the Internet, but I figured it was worth sharing mine here. The prompt&rsquo;s code is adapted from <a href="">this GitHub Gist</a>, but incorporates features from other examples I&rsquo;ve come across, namely:</p>
  2383. <ul>
  2384. <li>Only appears if your current directory is a Git repository.</li>
  2385. <li>Shows number of commits ahead and behind upstream, as applicable.</li>
  2386. <li>Shows if a merge is currently taking place.</li>
  2387. <li>Shows a &ldquo;traffic light&rdquo; representation of <code>git status</code>:
  2388. <ul>
  2389. <li>Red (<!-- raw HTML omitted -->●<!-- raw HTML omitted -->) means there are untracked changes.</li>
  2390. <li>Yellow (<!-- raw HTML omitted -->●<!-- raw HTML omitted -->) means there are unstaged changes.</li>
  2391. <li>Green (<!-- raw HTML omitted -->●<!-- raw HTML omitted -->) means there are staged changes.</li>
  2392. </ul>
  2393. </li>
  2394. </ul>
  2395. <p>Here&rsquo;s a contrived example that showcases the prompt (click on it for a larger version):</p>
  2396. <p><!-- raw HTML omitted --><img src="/post_assets/2012/12/git_zsh_prompt.png" alt="Git Prompt for Zsh"><!-- raw HTML omitted --></p>
  2397. <p>Here&rsquo;s the code for the prompt, as of this writing. (If I make any changes to the code in the future, the most up-to-date version will always be available <a href="">as a GitHub Gist</a>.) You can paste this code directly into your <code>.zshrc</code>, or save it in its own file and source that file in your <code>.zshrc</code>.</p>
  2398. <div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-zsh" data-lang="zsh"><span style="color:#75715e"># Adapted from code found at &lt;;.</span>
  2400. setopt prompt_subst
  2401. autoload -U colors <span style="color:#f92672">&amp;&amp;</span> colors <span style="color:#75715e"># Enable colors in prompt</span>
  2403. <span style="color:#75715e"># Modify the colors and symbols in these variables as desired.</span>
  2404. GIT_PROMPT_SYMBOL<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;%{</span>$fg<span style="color:#e6db74">[blue]%}±&#34;</span>
  2405. GIT_PROMPT_PREFIX<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;%{</span>$fg<span style="color:#e6db74">[green]%}[%{</span>$reset_color<span style="color:#e6db74">%}&#34;</span>
  2406. GIT_PROMPT_SUFFIX<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;%{</span>$fg<span style="color:#e6db74">[green]%}]%{</span>$reset_color<span style="color:#e6db74">%}&#34;</span>
  2407. GIT_PROMPT_AHEAD<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;%{</span>$fg<span style="color:#e6db74">[red]%}ANUM%{</span>$reset_color<span style="color:#e6db74">%}&#34;</span>
  2408. GIT_PROMPT_BEHIND<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;%{</span>$fg<span style="color:#e6db74">[cyan]%}BNUM%{</span>$reset_color<span style="color:#e6db74">%}&#34;</span>
  2409. GIT_PROMPT_MERGING<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;%{</span>$fg_bold<span style="color:#e6db74">[magenta]%}⚡︎%{</span>$reset_color<span style="color:#e6db74">%}&#34;</span>
  2410. GIT_PROMPT_UNTRACKED<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;%{</span>$fg_bold<span style="color:#e6db74">[red]%}●%{</span>$reset_color<span style="color:#e6db74">%}&#34;</span>
  2411. GIT_PROMPT_MODIFIED<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;%{</span>$fg_bold<span style="color:#e6db74">[yellow]%}●%{</span>$reset_color<span style="color:#e6db74">%}&#34;</span>
  2412. GIT_PROMPT_STAGED<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;%{</span>$fg_bold<span style="color:#e6db74">[green]%}●%{</span>$reset_color<span style="color:#e6db74">%}&#34;</span>
  2414. <span style="color:#75715e"># Show Git branch/tag, or name-rev if on detached head</span>
  2415. parse_git_branch<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
  2416.  <span style="color:#f92672">(</span>git symbolic-ref -q HEAD <span style="color:#f92672">||</span> git name-rev --name-only --no-undefined --always HEAD<span style="color:#f92672">)</span> 2&gt; /dev/null
  2417. <span style="color:#f92672">}</span>
  2419. <span style="color:#75715e"># Show different symbols as appropriate for various Git repository states</span>
  2420. parse_git_state<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
  2422.  <span style="color:#75715e"># Compose this value via multiple conditional appends.</span>
  2423.  local GIT_STATE<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;&#34;</span>
  2425.  local NUM_AHEAD<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;</span><span style="color:#66d9ef">$(</span>git log --oneline @<span style="color:#f92672">{</span>u<span style="color:#f92672">}</span>.. 2&gt; /dev/null | wc -l | tr -d <span style="color:#e6db74">&#39; &#39;</span><span style="color:#66d9ef">)</span><span style="color:#e6db74">&#34;</span>
  2426.  <span style="color:#66d9ef">if</span> <span style="color:#f92672">[</span> <span style="color:#e6db74">&#34;</span>$NUM_AHEAD<span style="color:#e6db74">&#34;</span> -gt <span style="color:#ae81ff">0</span> <span style="color:#f92672">]</span>; <span style="color:#66d9ef">then</span>
  2427.    GIT_STATE<span style="color:#f92672">=</span>$GIT_STATE<span style="color:#e6db74">${</span>GIT_PROMPT_AHEAD//NUM/$NUM_AHEAD<span style="color:#e6db74">}</span>
  2428.  <span style="color:#66d9ef">fi</span>
  2430.  local NUM_BEHIND<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;</span><span style="color:#66d9ef">$(</span>git log --oneline [email protected]<span style="color:#f92672">{</span>u<span style="color:#f92672">}</span> 2&gt; /dev/null | wc -l | tr -d <span style="color:#e6db74">&#39; &#39;</span><span style="color:#66d9ef">)</span><span style="color:#e6db74">&#34;</span>
  2431.  <span style="color:#66d9ef">if</span> <span style="color:#f92672">[</span> <span style="color:#e6db74">&#34;</span>$NUM_BEHIND<span style="color:#e6db74">&#34;</span> -gt <span style="color:#ae81ff">0</span> <span style="color:#f92672">]</span>; <span style="color:#66d9ef">then</span>
  2432.    GIT_STATE<span style="color:#f92672">=</span>$GIT_STATE<span style="color:#e6db74">${</span>GIT_PROMPT_BEHIND//NUM/$NUM_BEHIND<span style="color:#e6db74">}</span>
  2433.  <span style="color:#66d9ef">fi</span>
  2435.  local GIT_DIR<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;</span><span style="color:#66d9ef">$(</span>git rev-parse --git-dir 2&gt; /dev/null<span style="color:#66d9ef">)</span><span style="color:#e6db74">&#34;</span>
  2436.  <span style="color:#66d9ef">if</span> <span style="color:#f92672">[</span> -n $GIT_DIR <span style="color:#f92672">]</span> <span style="color:#f92672">&amp;&amp;</span> test -r $GIT_DIR/MERGE_HEAD; <span style="color:#66d9ef">then</span>
  2437.    GIT_STATE<span style="color:#f92672">=</span>$GIT_STATE$GIT_PROMPT_MERGING
  2438.  <span style="color:#66d9ef">fi</span>
  2440.  <span style="color:#66d9ef">if</span> <span style="color:#f92672">[[</span> -n <span style="color:#66d9ef">$(</span>git ls-files --other --exclude-standard 2&gt; /dev/null<span style="color:#66d9ef">)</span> <span style="color:#f92672">]]</span>; <span style="color:#66d9ef">then</span>
  2441.    GIT_STATE<span style="color:#f92672">=</span>$GIT_STATE$GIT_PROMPT_UNTRACKED
  2442.  <span style="color:#66d9ef">fi</span>
  2444.  <span style="color:#66d9ef">if</span> ! git diff --quiet 2&gt; /dev/null; <span style="color:#66d9ef">then</span>
  2445.    GIT_STATE<span style="color:#f92672">=</span>$GIT_STATE$GIT_PROMPT_MODIFIED
  2446.  <span style="color:#66d9ef">fi</span>
  2448.  <span style="color:#66d9ef">if</span> ! git diff --cached --quiet 2&gt; /dev/null; <span style="color:#66d9ef">then</span>
  2449.    GIT_STATE<span style="color:#f92672">=</span>$GIT_STATE$GIT_PROMPT_STAGED
  2450.  <span style="color:#66d9ef">fi</span>
  2452.  <span style="color:#66d9ef">if</span> <span style="color:#f92672">[[</span> -n $GIT_STATE <span style="color:#f92672">]]</span>; <span style="color:#66d9ef">then</span>
  2453.    echo <span style="color:#e6db74">&#34;</span>$GIT_PROMPT_PREFIX$GIT_STATE$GIT_PROMPT_SUFFIX<span style="color:#e6db74">&#34;</span>
  2454.  <span style="color:#66d9ef">fi</span>
  2456. <span style="color:#f92672">}</span>
  2458. <span style="color:#75715e"># If inside a Git repository, print its branch and state</span>
  2459. git_prompt_string<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
  2460.  local git_where<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;</span><span style="color:#66d9ef">$(</span>parse_git_branch<span style="color:#66d9ef">)</span><span style="color:#e6db74">&#34;</span>
  2461.  <span style="color:#f92672">[</span> -n <span style="color:#e6db74">&#34;</span>$git_where<span style="color:#e6db74">&#34;</span> <span style="color:#f92672">]</span> <span style="color:#f92672">&amp;&amp;</span> echo <span style="color:#e6db74">&#34;</span>$GIT_PROMPT_SYMBOL<span style="color:#66d9ef">$(</span>parse_git_state<span style="color:#66d9ef">)</span>$GIT_PROMPT_PREFIX<span style="color:#e6db74">%{</span>$fg<span style="color:#e6db74">[yellow]%}</span><span style="color:#e6db74">${</span>git_where#(refs/heads/|tags/)<span style="color:#e6db74">}</span>$GIT_PROMPT_SUFFIX<span style="color:#e6db74">&#34;</span>
  2462. <span style="color:#f92672">}</span>
  2464. <span style="color:#75715e"># Set the right-hand prompt</span>
  2465. RPS1<span style="color:#f92672">=</span><span style="color:#e6db74">&#39;$(git_prompt_string)&#39;</span>
  2466. </code></pre></div><p>I hope the prompt is as useful and as big of a time saver for you as it is for me!</p>
  2467. ]]>
  2468.    </content>
  2469.  </entry><entry>
  2470.    <title>Rejecting False Binary Files in Git</title>
  2471.    <link rel="alternate" type="text/html" href="" />
  2472.    <id>,2012:/2012/11/24/rejecting_false_binary_files_in_git.html</id>
  2473.    <published>2012-11-24T00:00:00-05:00</published>
  2474.    <updated>2012-11-24T00:00:00-05:00</updated>
  2475.    <author>
  2476.      <name>Josh Dick</name>
  2477.      <uri></uri>
  2478.    </author>
  2479.    <content type="html" xml:lang="en">
  2480.        <![CDATA[<blockquote>When text files stay up past their bedtime.</blockquote><h1 id="the-problem">The Problem</h1>
  2481. <p>I noticed a small but annoying issue with <a href="">Git</a> that surfaced every once in a while: Git would suddenly start treating text files as if they were binary files. This example output from a <a href="">relevant Stack Overflow question</a> illustrates the issue:</p>
  2482. <pre><code>$ git diff MyFile.txt
  2483. diff --git a/MyFile.txt b/MyFile.txt
  2484. index d41a4f3..15dcfa2 100644
  2485. Binary files a/MyFile.txt and b/MyFile.txt differ
  2486. </code></pre>
  2487. <p>In general, this issue could be viewed as a limitation of Git&rsquo;s built-in diff capability, since it Git <a href="">apparently is not great</a> at comparing files that use <a href="">variable-width encoding</a>. For my job however, none of the source code our team works on is supposed to use variable-width encoding. For our purposes, it&rsquo;s safe to assume that seeing this issue means that a developer mistakenly added non-ASCII characters to an otherwise-ASCII text file (Git&rsquo;s limitations notwithstanding.)</p>
  2488. <p>I decided to create a <a href="">Git update hook</a> to reject problem commits when developers try to push them so these mistakes could be caught in an automated fashion when they happened, rather than having developers figure out when and why their diffs suddenly stopped working.</p>
  2489. <h1 id="the-code">The Code</h1>
  2490. <div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-bash" data-lang="bash"><span style="color:#75715e">#!/bin/bash
  2491. </span><span style="color:#75715e"></span>
  2492. #
  2493. <span style="color:#75715e"># [Your existing update hook code here...]</span>
  2494. #
  2496. refname<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;</span>$1<span style="color:#e6db74">&#34;</span>
  2497. oldrev<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;</span>$2<span style="color:#e6db74">&#34;</span>
  2498. newrev<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;</span>$3<span style="color:#e6db74">&#34;</span>
  2500. <span style="color:#75715e"># --- Reject this commit if it contains source files that Git views as binary files.</span>
  2502. <span style="color:#75715e"># First, make sure user is pushing a new branch and not deleting one. ($newrev will be all zeros when deleting.)</span>
  2503. zero<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;0000000000000000000000000000000000000000&#34;</span>
  2504. <span style="color:#66d9ef">if</span> <span style="color:#f92672">[</span> <span style="color:#e6db74">&#34;</span>$newrev<span style="color:#e6db74">&#34;</span> !<span style="color:#f92672">=</span> <span style="color:#e6db74">&#34;</span>$zero<span style="color:#e6db74">&#34;</span> <span style="color:#f92672">]</span>; <span style="color:#66d9ef">then</span>
  2506.  <span style="color:#75715e"># Tests whether Git thinks the passed filename ($1) is a binary file.</span>
  2507.  isBinary<span style="color:#f92672">()</span> <span style="color:#f92672">{</span>
  2508.    binaryPattern<span style="color:#f92672">=</span><span style="color:#66d9ef">$(</span>printf <span style="color:#e6db74">&#39;%s\t-\t&#39;</span> -<span style="color:#66d9ef">)</span>;
  2509.    diffResult<span style="color:#f92672">=</span><span style="color:#66d9ef">$(</span>git diff --numstat master $newrev -- <span style="color:#e6db74">&#34;</span>$1<span style="color:#e6db74">&#34;</span><span style="color:#66d9ef">)</span>;
  2510.    <span style="color:#66d9ef">return</span> <span style="color:#66d9ef">$(</span><span style="color:#f92672">[[</span> <span style="color:#e6db74">&#34;</span>$diffResult<span style="color:#e6db74">&#34;</span> <span style="color:#f92672">=</span>~ <span style="color:#e6db74">&#34;</span>$binaryPattern<span style="color:#e6db74">&#34;</span> <span style="color:#f92672">]]</span><span style="color:#66d9ef">)</span>
  2511.  <span style="color:#f92672">}</span>
  2513.  <span style="color:#75715e"># Get a list of all relevant files to check: filter the names of all changed files in $newrev by extension.</span>
  2514.  checkFiles<span style="color:#f92672">=</span><span style="color:#66d9ef">$(</span>git show --pretty<span style="color:#f92672">=</span><span style="color:#e6db74">&#34;format:&#34;</span> --name-only $newrev | grep -E <span style="color:#e6db74">&#39;\.(java|groovy|js|xml|css|less|sh)(\..+)?$&#39;</span><span style="color:#66d9ef">)</span>
  2516.  binaryFilesFound<span style="color:#f92672">=</span>false
  2517.  <span style="color:#66d9ef">while</span> read -r filename; <span style="color:#66d9ef">do</span>
  2518.      <span style="color:#66d9ef">if</span> <span style="color:#f92672">[</span> ! -z $filename <span style="color:#f92672">]</span> <span style="color:#f92672">&amp;&amp;</span> <span style="color:#66d9ef">$(</span>isBinary $filename<span style="color:#66d9ef">)</span>; <span style="color:#66d9ef">then</span>
  2519.        echo <span style="color:#e6db74">&#34;*** File </span>$filename<span style="color:#e6db74"> appears to be a binary file, but should be plain text.&#34;</span> &gt;&amp;<span style="color:#ae81ff">2</span>
  2520.        binaryFilesFound<span style="color:#f92672">=</span>true
  2521.      <span style="color:#66d9ef">fi</span>
  2522.  <span style="color:#66d9ef">done</span> <span style="color:#f92672">&lt;&lt;&lt;</span> <span style="color:#e6db74">&#34;</span>$checkFiles<span style="color:#e6db74">&#34;</span>
  2524.  <span style="color:#66d9ef">if</span> $binaryFilesFound; <span style="color:#66d9ef">then</span>
  2525.    echo <span style="color:#e6db74">&#34;Please remove all non-human-readable characters from the above file(s).&#34;</span>
  2526.    echo <span style="color:#e6db74">&#34;For example, to remove NUL characters from a file:&#34;</span>
  2527.    echo <span style="color:#e6db74">&#34;  tr &lt; file.ext -d &#39;\000&#39; &gt; file.tmp&#34;</span>
  2528.    echo <span style="color:#e6db74">&#34;  mv file.tmp file.ext&#34;</span>
  2529.    <span style="color:#75715e"># Reject the push</span>
  2530.    exit 1;
  2531.  <span style="color:#66d9ef">fi</span>
  2533. <span style="color:#66d9ef">fi</span>
  2535. <span style="color:#75715e"># --- Finished</span>
  2536. exit <span style="color:#ae81ff">0</span>
  2537. </code></pre></div><h1 id="how-it-works">How it Works</h1>
  2538. <p>This code lives inside the update hook script (<code>hooks/update</code>) in our central Git repository. It runs on the server whenever someone does a <code>git push</code>.</p>
  2539. <p>Here&rsquo;s a summary of what the code does:</p>
  2540. <ol>
  2541. <li>Get a list of all files to be changed in the new revision (incoming pushed changes).</li>
  2542. <li>Filter the list of files by their extensions, so that the list only contains files that are supposed to be plain text files.</li>
  2543. <li>For each file in the list, make sure that the incoming changes to that file don&rsquo;t cause Git to treat the file as binary data.</li>
  2544. <li>If any of the files fail this test, reject the push and show the user an explanatory error so they can fix the problem before attempting to push again.</li>
  2545. </ol>
  2546. <h1 id="considerations">Considerations</h1>
  2547. <p>Using an update hook isn&rsquo;t the ideal solution, since an ideal solution would prevent this type of mistake from being made at all. However, the update hook does prevent developers from accidentally propagating problematic changes.</p>
  2548. <p>If you know of a better way to solve this problem, I&rsquo;d love to hear about it!</p>
  2549. ]]>
  2550.    </content>
  2551.  </entry>
  2552. </feed>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid Atom 1.0" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda