<?xml version="1.0"?>
<?xml-stylesheet href="/transform" type="text/xsl"?>
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:bibo="http://purl.org/ontology/bibo/" xmlns:bs="http://purl.org/ontology/bibo/status/" xmlns:ci="https://vocab.methodandstructure.com/content-inventory#" xmlns:dct="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:xhv="http://www.w3.org/1999/xhtml/vocab#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" lang="en" prefix="bibo: http://purl.org/ontology/bibo/ bs: http://purl.org/ontology/bibo/status/ ci: https://vocab.methodandstructure.com/content-inventory# dct: http://purl.org/dc/terms/ foaf: http://xmlns.com/foaf/0.1/ rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns# xhv: http://www.w3.org/1999/xhtml/vocab# xsd: http://www.w3.org/2001/XMLSchema#" vocab="http://www.w3.org/1999/xhtml/vocab#" xml:lang="en">
  <head>
    <title property="dct:title">The Distraction Account</title>
    <base href="https://doriantaylor.com/the-distraction-account"/>
    <link href="document-stats#EOhroHGPjujuJgmDyIH2hK" rev="ci:document"/>
    <link href="elsewhere" rel="alternate bookmark" title="Elsewhere"/>
    <link href="this-site" rel="alternate index" title="This Site"/>
    <link href="http://purl.org/ontology/bibo/status/published" rel="bibo:status"/>
    <link href="" rel="ci:canonical" title="The Distraction Account"/>
    <link href="lexicon/#E-ZY5i7K1cqzfT0p1L9ajJ" rel="dct:audience" title="Digital Media Practitioner"/>
    <link href="person/dorian-taylor#me" rel="dct:creator" title="Dorian Taylor"/>
    <link href="http://ideaconference.org/2006/audio/02%20Linda%20Stone%20-%20Opening%20Keynote.mp3" rel="dct:references"/>
    <link href="person/dorian-taylor" rel="meta" title="Who I Am"/>
    <link about="./" href="3f36c30c-6096-454a-8a22-c062100ae41f" rel="alternate" type="application/atom+xml"/>
    <link about="./" href="f07f5044-01bc-472d-9079-9b07771b731c" rel="alternate" type="application/atom+xml"/>
    <link about="./" href="this-site" rel="alternate"/>
    <link about="./" href="elsewhere" rel="alternate"/>
    <link about="./" href="e341ca62-0387-4cea-b69a-cdabc7656871" rel="alternate" type="application/atom+xml"/>
    <link about="verso/" href="3f36c30c-6096-454a-8a22-c062100ae41f" rel="alternate" type="application/atom+xml"/>
    <link about="verso/" href="this-site" rel="alternate"/>
    <link about="verso/" href="elsewhere" rel="alternate"/>
    <meta content="the-distraction-account" datatype="xsd:token" property="ci:canonical-slug"/>
    <meta content="In this article, I evaluate a means of mitigating the distractions that impede on the productivity of creative work, specifically that on computers by way of relegating network-originated distractions to a separate account." name="description" property="dct:abstract"/>
    <meta content="2009-06-19T09:40:06+00:00" datatype="xsd:dateTime" property="dct:created"/>
    <meta content="the-distraction-account" property="dct:identifier"/>
    <meta content="2009-06-19T09:44:40+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2022-05-31T04:18:52+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2022-05-31T15:10:50+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta about="person/dorian-taylor#me" content="Dorian Taylor" name="author" property="foaf:name"/>
    <meta content="summary" name="twitter:card"/>
    <meta content="@doriantaylor" name="twitter:site"/>
    <meta content="The Distraction Account" name="twitter:title"/>
    <meta content="In this article, I evaluate a means of mitigating the distractions that impede on the productivity of creative work, specifically that on computers by way of relegating network-originated distractions to a separate account." name="twitter:description"/>
    <object>
      <nav>
        <ul>
          <li>
            <a href="document-stats#EOhroHGPjujuJgmDyIH2hK" rev="ci:document" typeof="qb:Observation">
              <span>urn:uuid:3a1ae81c-63e3-4ba3-ab89-8260f2207da1</span>
            </a>
          </li>
        </ul>
      </nav>
    </object>
  </head>
  <body about="" id="EYbqGwQ1Vea9pkD1za4IZL" typeof="bibo:Article">
    <p>The work of creative professionals is that which enjoys <a href="introducing-the-cell" title="Introducing the Cell" rel="dct:references">long, contiguous blocks</a> of concentration and undivided attention. I leave the case of whether it <em>demands</em> such conditions open to debate, but I assert that fostering concentration <em>won't hurt</em> performance, and it's unlikely that one would miss much in the meanwhile. My solution &#x2014; admittedly an experiment &#x2014; is to eradicate all sources of distraction on my main computer, and sequester them elsewhere.</p>
    <aside role="note" id="Ea3sOiyGJIFKuFfa8zAyMJ">When I went to write about my newfound strategy, I discovered that <a href="http://www.paulgraham.com/distraction.html" title="Disconnecting Distraction" rel="dct:references">Paul Graham</a> had beaten me to the punch. He notes that the <a href="http://en.wikipedia.org/wiki/WIMP_(computing)" title="WIMP (computing) &#x2014; Wikipedia" rel="dct:references"><acronym title="Windows, Icons, Menus, Pointer">WIMP</acronym></a> interface paradigm that dominates personal computing underwent the bulk of its evolution as a means of facilitating <em>solitary</em> work, before we could dream of each machine possessing a persistent, high-bandwidth connection to an endless stream of <em>attention-crack</em>. He argues that the <a rel="dct:references xhv:glossary" href="lexicon/form" title="Form">form</a> of the interaction can't support the onslaught of chimes, notifications and dialogue boxes that a network connection inevitably generates. <span class="parenthesis" title="I know it isn't en vogue to agree with Paul Graham, but I'm going to break from the herd on this one.">I enthusiastically agree</span>, and I add that as users of these systems, <em>neither can we</em> &#x2014; and nor should we, as most of these interruptions are frivolous. As attention sage <a href="http://www.lindastone.net/" title="(Linda Stone's Thoughts on Attention and Specifically, Continuous Partial Attention)" rel="dct:references">Linda Stone</a> says: <q cite="http://ideaconference.org/2006/audio/02%20Linda%20Stone%20-%20Opening%20Keynote.mp3">Which of these emails is a tiger, and which are flies?</q></aside>
    <section id="E7nCXzySHhO2cKq5H2u0jL">
      <h2>A Separate Computer</h2>
      <p>In my first attempt, I <span class="parenthesis" title="similar to what Paul Graham prescribes in the aforementioned article">set up a laptop</span> to handle my mail, feeds, messaging and serendipitous <abbr title="World-Wide Web">Web</abbr> browsing. I perched it at the edge of my desk farthest from my main machine, which was far enough away that I would have to reorient myself to use it. This provided a solid separation of cognitive contexts &#x2014; I could be in <em>work mode</em> one instant, pivot and goof off the next. Any files I generated on either machine, I would shunt to a common shared folder. I would ship links and text snippets back and forth by pasting them into a terminal that was <span class="parenthesis" title="via screen(1), of course.">open on both machines</span> to the same shell. I disabled all chimes and notifications. When the <em>Distraction Laptop's</em> screen-saver was on, it was as if it wasn't there.</p>
      <aside role="note" id="E2BA3ZQDIPWWNvlr8PS8XJ">While this solution worked for the most part, there were a few issues. First, it was possible to monitor both the workstation and the laptop at the same time, <span class="parenthesis" title="I understand why Paul Graham admonishes to put each machine on opposite sides of the room.">essentially obviating the point</span> of separating functions between the two. I disciplined myself to lock the laptop's screen when it was time to work, with the requirement to enter a password providing an additional hurdle to keep me on task. I incurred extra setup overhead, and it was also a somewhat baroque experience moving information back and forth between the two machines. Finally, using the laptop for anything other than goofing off &#x2014; say, on the road &#x2014; would pollute its frivolity-only purpose. All this is is moot anyway, because a piece of fluff or something got caught in its main fan and now it <span class="parenthesis" title="of course making it impossible to use. I suppose I could spend an afternoon fixing it, but I need a new laptop anyway.">sounds like a lawnmower</span>.</aside>
    </section>
    <section id="EzN229ICLUfUt6iLv8jUUI">
      <h2>A Second Account</h2>
      <p>With the <em>Distraction Laptop</em> out of commission, I found all my computing tasks once again unceremoniously lumped onto the same screen, and my productivity grinding to a halt. In a pinch, I set up a new account and transplanted the laptop's settings to it. This is the configuration I use <ins datetime="2009-06-19" title="June 19, 2009">for now</ins>.</p>
      <aside role="note" id="EyGo9ogZQkQ9u0aGsWhoJI">As an aside, a second, limited account is a remarkably simple and elegant solution, regardless of operating system, to mitigate the damage caused by a virus infection. Assuming the account <span class="parenthesis" title="you will likely have to set that up manually">can't write outside</span> its own home directory and the attack <span class="parenthesis" title="And most don't &#x2014; remote root exploits don't happen nearly as often as double-clicking on the wrong icon.">doesn't escalate privileges</span>, any compromise will be contained within.</aside>
      <p>Of course, with both accounts on the same machine, I can only see one at once, and must enter a password to switch between the two, so I'm not as tempted to wander. Furthermore, I don't need to physically contort myself to switch tasks, which, although I didn't mind, was probably bad for ergonomics. My experience with two accounts on the same machine, however, is a bit disorienting. With the laptop, both accounts were <em>me</em>. Consolidated to one machine, I have <em>me</em> and <em>not-exactly-me</em>, which raises some annoying questions. Do I manage two <abbr title="Secure SHell">SSH</abbr> agents? Do I mount the same share twice? Do I try to consolidate these? What about settings? Getting the two accounts to speak with each other, a no-brainer with two machines, is suddenly riddled with uncertainties. <span class="parenthesis" title="that is, when I open that sucker up and blow out the dust bunnies, or get a new laptop altogether.">I may well revert</span> to my original configuration soon, or try something else entirely.</p>
      <aside role="note" id="EAIKlBiTkccwVnnlJQl31L">On Mac OS X, the fast-user-switching functionality stops iTunes from playing when switching from one account to the next. While I understand why Apple's designers chose to do this, it is positively <em>grating</em>. I'm sure some property-list mangling can be done to change this behaviour, but I don't currently have the fortitude to go digging through the reams of Mac forums and mailing lists to find it.</aside>
    </section>
    <section id="E5eZEPP4J2In_Nrp9jPq_J">
      <h2>What Doesn't Work</h2>
      <p>The <span class="parenthesis" title="those who know me would snicker, but I swear, it exists">staunch pragmatist</span> in me posited that it was a waste of effort to create and configure a separate account for the purposes, especially with the aforementioned shortcomings. Why not, instead, just relegate the distraction-causing programs to a separate virtual desktop?</p>
      <p>The simple answer is that it isn't enough. Chatty software can still reach me through the dock, taskbar or with a dialogue box. This is exacerbated by the fact that a mere keypress gives me instant access to these tantalizing time-suckers. Moreover, I still use common tools, <span class="parenthesis" title="actually, several browsers">such as a browser</span>, to do actual work.</p>
    </section>
    <section id="E_co8NfjAkZhY1s1rHL-ZL">
      <h2>An Optimal Solution</h2>
      <p>Like many divergent design requirements, my desires for uninterrupted concentration and the ability to monitor my daily trivia are not completely orthogonal. When I am working, there <em>are</em> a <span class="parenthesis" title="most of which happen in meatspace"><em>choice few</em> events</span> important enough to usurp my attention, despite that number approaching zero. Moreover, I <em>will</em> want to <em>send</em> messages, as well as <em>import</em> and <em>consolidate</em> salient information from messages I receive.</p>
      <p>What I <em>want</em> is to <em>prevent all software</em> from stealing focus, making noise, causing strobing visuals or really generating any notifications whatsoever, without my express permission. The manner in which I <em>do</em> want to be notified is in a way that is commensurate with <em>how important <strong>I</strong> feel it is</em>. I also want to take action items <em>out</em> of the monsoon of network-originated events and bring them with me into my serene bubble of productivity, where I can work on them in peace.</p>
      <p>Despite this rigmarole, there is a constant. Without clear objectives, effective methods for achieving them and the necessary space, tools, information and resources, even the most elaborate technical solution is toothless. Without a solid work plan and a realistic means of carrying it out, we will procrastinate and go looking for distractions. Clarity and discipline are perhaps the best productivity tools of all.</p>
    </section>
  </body>
</html>
