<?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">Reverse Polish Notation for People</title>
    <base href="https://doriantaylor.com/reverse-polish-notation-for-people"/>
    <link href="document-stats#Eh7JbDkf-53-xNUeyELvWJ" 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="Reverse Polish Notation for People"/>
    <link href="lexicon/#EzqXIsriaILFcWjXdS7FbI" rel="dct:audience" title="Software Developer"/>
    <link href="person/dorian-taylor#me" rel="dct:creator" title="Dorian Taylor"/>
    <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="reverse-polish-notation-for-people" datatype="xsd:token" property="ci:canonical-slug"/>
    <meta content="Reverse Polish Notation is an extremely economical way to make sense to computers at the cost of making sense to people. But what about applying the same principle to arrange language in a way that is most useful to people?" name="description" property="dct:abstract"/>
    <meta content="2009-12-17T09:19:14+00:00" datatype="xsd:dateTime" property="dct:created"/>
    <meta content="reverse-polish-notation-for-people" property="dct:identifier"/>
    <meta content="2009-12-18T03:34:19+00:00" datatype="xsd:dateTime" property="dct:issued"/>
    <meta content="2009-12-18T00:19:13+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2009-12-18T03:35:18+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2009-12-18T03:39:09+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2009-12-18T03:45:02+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2009-12-18T03:49:58+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2009-12-18T03:50:43+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2009-12-18T09:20:29+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="Reverse Polish Notation for People" name="twitter:title"/>
    <meta content="Reverse Polish Notation is an extremely economical way to make sense to computers at the cost of making sense to people. But what about applying the same principle to arrange language in a way that is most useful to people?" name="twitter:description"/>
    <object>
      <nav>
        <ul>
          <li>
            <a href="document-stats#Eh7JbDkf-53-xNUeyELvWJ" rev="ci:document" typeof="qb:Observation">
              <span>urn:uuid:87b25b0e-47fe-4e77-9fb1-3547b210bbd6</span>
            </a>
          </li>
        </ul>
      </nav>
    </object>
  </head>
  <body about="" id="EC-3FgM2CjoGH2NJInus3J" typeof="bibo:Article">
    <section id="ElMwKPBeVjr-UP4i5616XI">
      <p><a href="http://en.wikipedia.org/wiki/Reverse_Polish_notation" title="Reverse Polish notation &#x2014; Wikipedia" rel="dct:references">Reverse Polish notation</a> is a way of stating a formal language such that the operators, or verbs, come at the end of a series of operands, or nouns, like this: <samp>1 2 +</samp> . In this configuration, a computer doesn't have to listen for very long or hold on to a lot of partial information before it can make sense of things and get to work. This behaviour makes it good for systems that don't have a lot of working memory or talk along slow communication channels, like <a href="http://en.wikipedia.org/wiki/Open_Firmware" title="Open Firmware &#x2014; Wikipedia" rel="dct:references">firmware</a>, <a href="http://en.wikipedia.org/wiki/PostScript" title="PostScript &#x2014; Wikipedia" rel="dct:references">printers</a> and <a href="http://en.wikipedia.org/wiki/RPL_programming_language" title="RPL programming language &#x2014; Wikipedia" rel="dct:references">calculators</a>.</p>
      <p>Know what else has very little working memory and communicates along a slow channel? <em>People</em>. They also don't have a lot of patience for things that take too long to understand or demonstrate value. What if, then, we could take the principle that makes reverse Polish notation go down so easily for computers, and apply it to people?</p>
    </section>
    <section id="Ei2V0RXzn11a7TsPlt7o9K">
      <h2>Did you just say what I think you said?</h2>
      <p>You might be thinking about how <acronym title="Reverse Polish Notation">RPN</acronym> has a reputation for just how <em>hard</em> it is for people to understand. Or you could be thinking about how, <a href="http://en.wikipedia.org/wiki/Subject_Object_Verb" rel="dct:references">lots of languages, notably Japanese</a>, basically already do that. <em>Or</em>, you could still be wondering what I'm talking about, indicating such a thing might be useful.</p>
      <p>Rest assured, I am not suggesting we start talking like Yoda. I'm thinking exclusively about applying the <em>principle</em> of feeding people information in an order most amenable to uptake. What I envision is a method of dynamically arranging text at around the paragraph level, all the way up the document outline. <a href="http://en.wikipedia.org/wiki/Hypertext" title="Hypertext &#x2014; Wikipedia" rel="dct:references">Hypertext</a> <span class="parenthesis" title="although most people don't capitalize on this very heavily with the Web.">implicitly does this already</span> by splitting documents into small pieces and weaving them together with links, enabling people to follow the <span class="parenthesis" title="Ever experience yourself getting lost in Wikipedia for several hours? Yeah. That.">path of least cognitive resistance</span>. I have performed some preliminary research into methods for untangling the hairball of hypertext and ironing it out into a linear format, such as one to be printed or spoken, and the results look promising.</p>
    </section>
    <section id="Ew5vXB_M13P4k_nECuvnDL">
      <h2>Isn't that basically what a good salesperson does?</h2>
      <p>Yes, and likewise a good storyteller or teacher. I argue that indeed there is a high degree of overlap in these professions. All are capable of sustaining their audiences' interests, and get them to understand the relevant information and appreciate it quickly, and stick around for the d&#xE9;nouement. I believe this can be made systematic. And of course, this is not to obsolesce our dear scriveners, teachers and sales force, but rather to make poor performers competent and good ones stellar.</p>
    </section>
    <aside role="note" id="EgTYdGoBqzZsIJrvjGqkuL">
      <p>Disclosure: Yes, I <em>can</em> write <a href="http://en.wikipedia.org/wiki/PostScript" title="PostScript &#x2014; Wikipedia" rel="dct:references">PostScript</a>.</p>
    </aside>
  </body>
</html>
