<?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">Design is the Second Derivative of Just Plain Doing Stuff</title>
    <base href="https://doriantaylor.com/b793b51e-ab28-4c23-8914-c5b0ca887829"/>
    <link href="document-stats#EW6gDeckEAtOuo4UdS0rwL" 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/draft" rel="bibo:status"/>
    <link href="http://purl.org/ontology/bibo/status/published" rel="bibo:status"/>
    <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="false" datatype="xsd:boolean" property="ci:indexed"/>
    <meta content="The first derivative is engineering. The third derivative is philosophy." name="description" property="dct:abstract"/>
    <meta content="2016-07-23T19:26:47+00:00" datatype="xsd:dateTime" property="dct:created"/>
    <meta content="2016-09-17T03:10:36+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2017-08-19T17:46:43+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2019-08-15T21:03:26+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2020-02-08T20:37:50+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="Design is the Second Derivative of Just Plain Doing Stuff" name="twitter:title"/>
    <meta content="The first derivative is engineering. The third derivative is philosophy." name="twitter:description"/>
    <object>
      <nav>
        <ul>
          <li>
            <a href="toys" rev="dct:requires" typeof="bibo:Article">
              <span property="dct:title">Toys</span>
            </a>
          </li>
          <li>
            <a href="document-stats#EW6gDeckEAtOuo4UdS0rwL" rev="ci:document" typeof="qb:Observation">
              <span>urn:uuid:5ba80379-c904-402d-b3ae-a3851d4b4af0</span>
            </a>
          </li>
        </ul>
      </nav>
    </object>
  </head>
  <body about="" id="Et5O1HqsowjkUxbDKiHgpI" typeof="bibo:Article">
    <p>proposal: design is the second derivative of just plain doing stuff</p>
    <p>hypothesis: we don't have a very good theory of the economics of design, because up until the last few decades we haven't really needed one</p>
    <p>why i'm interested: sick of being on the hook for externalities</p>
    <p>why you might be interested: even if you don't care about my success, your success is inextricably linked to my success</p>
    <hr/>
    <p>Taming the risk of what I term <dfn>highly-synthetic work</dfn> has been a central theme in my independent research for several years now. Highly-synthetic work, as I am defining it, is that which passes through a long chain of feedback loops to get to the end state&#x2014;if there <em>is</em> such a thing&#x2014;and likewise for which the cost of information-gathering, cognitive processing and communication, far outstrips the cost of materials and rote labour. In other words, a highly-synthetic artifact costs way more to <em>design</em> than to <q>build</q>.</p>
    <section id="ED46_fjPUT8M1na7dNP2sL">
      <h2><q>Building</q> as Anchor and Counterweight</h2>
      <p>Conventional engineering projects are governed on two sides by material constraints: the physical properties of the materials that dictate their performance, and the economics of acquiring said physical materials, and physically arranging them in space.</p>
      <p>For example: if you wish to construct a building, it is a fairly straightforward formula to go from intended use to square footage, <span class="parenthesis" title="assuming you already own it">which when crossed with the building site</span>, will yield roughly the expected number of floors, staircases, doors, windows, <abbr title="heating, ventilation, air conditioning">HVAC</abbr> machinery, elevators and bathrooms, as well as the quantity of concrete, steel, plumbing, ducting, wire, doorknobs, fixtures, et cetera. Take that figure and double it, as construction labour currently costs roughly the same as materials. Then, add an additional 25%&#x2014;i.e., 20% of 100%&#x2014;to be divided as needed between the architect and structural engineer. The result is a fairly accurate <a rel="dct:references" href="https://en.wikipedia.org/wiki/Fermi_problem" title="Fermi problem &#x2014; Wikipedia">Fermi-like estimate</a> for the scope of an ordinary construction project.</p>
      <figure id="construction-cost-structure">
        <h6 style="text-align: center; text-transform: none">Cost Structure of a Construction Project</h6>
        <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" id="EDeAEp-vwtkAlFW5ZsIurK" style="margin: 1em auto" width="480px" height="80px">
          <g id="diagram" transform="translate(40, 0)">
            <rect id="reference" x="0" y="20" width="400" height="20" fill="black"/>
            <rect id="design" x="0" y="20" width="80" height="20" fill="#333"/>
            <rect id="engineering" x="48" y="20" width="32" height="20" fill="#666"/>
            <rect id="construction" x="80" y="20" width="320" height="20" fill="#222"/>
            <rect id="labour" x="80" y="20" width="160" height="20" fill="#444"/>

            <a id="design-construction" class="slider" transform="translate(80,0)" xlink:href="javascript:;" xlink:title="Design/Construction">
              <polygon points="-20,2 -18,0 18,0 20,2 20,10 18,12 8,12 0,20 -8,12 -18,12 -20,10"/>
              <text x="0" y="6" dominant-baseline="central" text-anchor="middle" font-size="10" fill="white">20.0%</text>
            </a>

            <a id="architect-engineer" class="slider" transform="translate(48,40)" xlink:href="javascript:;" xlink:title="Architecture/Structural Engineering">
              <polygon points="-40,10 -38,8 -8,8 0,0 0,18 -2,20 -38,20 -40,18"/>
              
              <text x="-20" y="14" dominant-baseline="central" text-anchor="middle" font-size="10" fill="white">12.0%</text>
            </a>

            <a id="materials-labour" class="slider" transform="translate(240,40)" xlink:href="javascript:;" xlink:title="Materials/Construction Labour">
              <polygon points="0,0 8,8 38,8 40,10 40,18 38,20 2,20 0,18"/>
              <text x="20" y="14" dominant-baseline="central" text-anchor="middle" font-size="10" fill="white">60.0%</text>
            </a>
            <g transform="translate(0,5)">
              <polyline id="scale" points="0,60 0,70 400,70 400,60" fill="none" stroke="black"/>
              <text id="scale-text" x="403" y="66" dominant-baseline="central" text-anchor="start" font-size="10" fill="black">$1M</text>
            </g>
          </g>
        </svg>
        <figcaption>
        <form id="table" class="madlibs">
        <table style="width: 80%; margin: auto" id="EzXx82aDwaQ12CFOCVsCPJ">
          <thead>
            <tr>
              <th><output class="percent" name="pct-design">20</output> Design: <output class="dollars" name="val-design">200,000</output></th>
              <th><output class="percent" name="pct-construct">80</output> Construction: <output class="dollars" name="val-construct">800,000</output></th>
            </tr>
          </thead>
          <tfoot>
            <tr>
              <th colspan="2" style="line-height: 3em">Total project cost, less real estate: <span class="dollars"><input class="dollars" name="prj-cost" style="width: 7em" type="number" value="1000000" min="1000" step="1000"/></span></th>
            </tr>
          </tfoot>
          <tbody>
            <tr>
              <td><output style="color: white; background-color: #333; border: 1px dashed black;" class="percent" name="pct-arch">12</output> Architecture: <output class="dollars" name="val-arch">120,000</output></td>
              <td><output style="color: white; background-color: #444; border: 1px dashed black;" class="percent" name="pct-labr">40</output> Labour: <output class="dollars" name="val-labr">400,000</output></td>
            </tr>
            <tr>
              <td><output style="color: white; background-color: #666; border: 1px dashed black;" class="percent" name="pct-eng">8</output> Engineering: <output class="dollars" name="val-eng">80,000</output></td>
              <td><output style="color: white; background-color: #222; border: 1px dashed black;" class="percent" name="pct-matl">40</output> Materials: <output class="dollars" name="val-matl">400,000</output></td>
            </tr>
          </tbody>
        </table>
        <p>Using an equivalent hourly rate of <span class="dollars"><input class="dollars" style="width: 3em" type="number" name="hourly-rate" value="200" min="1" step="1"/></span> as a benchmark, and handwaving away capital spent on research, experimentation and presentation materials, we can see that around <output style="font-weight: bold" name="practitioner-hours">600</output> <select onchange="this.form.recalculate()" name="toggle-discipline"><option value="arch">architect</option><option value="eng">engineer</option></select>-hours are appropriate for a project of this size.</p>
        </form>
        <script type="text/javascript" src="asset/form-utilities" rel="dct:requires"></script>
        <script type="text/javascript" src="asset/svg-utilities" rel="dct:requires"></script>
        <script type="text/javascript">
          (function () {
            var svg  = document.getElementById('EDeAEp-vwtkAlFW5ZsIurK');
            var form = document.getElementById('table');

            var genBoundary = function (target, property) {
              var node = document.getElementById(target);
              if (!node) throw 'no node with ID ' + target;
              if (property) return function () {
                return node[property].baseVal.value; };
              return function () {
                var bv = node.transform.baseVal;
                var xf = bv.consolidate() || bv.createSVGTransformFromMatrix(
                  node.ownerSVGElement.createSVGMatrix());
                return xf.matrix.e;
              };
            };

            var setupSVG = function (obj) {
              var ref  = document.getElementById('reference');
              var elem = document.getElementById(obj.id);
              elem.textNode = elem.getElementsByTagName('text')[0].firstChild;
              elem.lhs = obj.lhs;
              elem.rhs = obj.rhs;
              elem.pp  = obj.pp;

              var dragOp = function(cursor, matrix) {
                var svg = this.ownerSVGElement;
                var tp  = cursor.matrixTransform(matrix);
                var bv  = this.transform.baseVal;
                var ct  = bv.consolidate() ||
                  bv.createSVGTransformFromMatrix(svg.createSVGMatrix());

                var off = cursor.x + matrix.e;
                var lhs = this.lhs();
                var rhs = this.rhs();

                if (off &gt; rhs)      off = rhs;
                else if (off &lt; lhs) off = lhs;

                ct.matrix.e = off;
                this.transform.baseVal.initialize(ct);

                /* now for the text */
                var ratio = off/ref.width.baseVal.value;
                this.textNode.data = ratio.asPercent();

                /* and now the postprocessor function */
                if (this.pp &amp;&amp; typeof this.pp === 'function') this.pp();
              };

              elem.bindDragOperation(dragOp);
            }

            var recalc = function () {
              var dollars = this['prj-cost'].value;
              var rects   = this.diagram.rects;
              var ref     = rects.reference.width.baseVal.value;

              var widths = {
                'design': rects.design.width.baseVal.value,
                'construct': rects.construction.width.baseVal.value,
                'eng': rects.engineering.width.baseVal.value,
                'labr': rects.labour.width.baseVal.value };
              widths['arch'] = widths['design'] - widths['eng'];
              widths['matl'] = widths['construct'] - widths['labr'];

              var cats = ['design', 'construct', 'arch', 'eng', 'labr', 'matl'];

              var ratios = {};
              cats.map(function (x) { ratios[x] = widths[x] / ref });

              var values = {};
              cats.map(function (x) { values[x] = ratios[x] * dollars });

              for (var i = 0; i &lt; cats.length; i++) {
                var which = cats[i];
                this['pct-' + which].value = (ratios[which] * 100).round(2);
                this['val-' + which].value = values[which].round();
              }

              /* now deal with hourly */
              var discipline = this['toggle-discipline'].value;
              var hourly = this['hourly-rate'].value;
              var ph = this['practitioner-hours'];
              ph.value = Math.floor(values[discipline] / hourly);
            };

            var changeForm = {
              'prj-cost': function (e) {
                 var val = FormUtils.coerceNumber(this.value);
                 if (val &lt; 1000) this.value = val = 1000;
                 this.form.diagram.setScale(val);
                 this.form.recalculate();
              },
              'hourly-rate': function (e) {
                 this.form.recalculate();
              }
            };

            var dcpp = function () {
              var svg = this.ownerSVGElement;
              var m = this.transform.baseVal.getItem(0).matrix;

              var le = svg.rects.engineering;
              var lx = le.x.baseVal.value;
              var lw = le.width.baseVal.value;
              le.width.baseVal.value = m.e - lx;

              var de = svg.rects.design;
              var dx = de.x.baseVal.value;
              var dw = de.width.baseVal.value;
              de.width.baseVal.value = m.e - dx;

              var ce = svg.rects.construction;
              var cx = ce.x.baseVal.value;
              var cw = ce.width.baseVal.value;
              ce.x.baseVal.value = m.e;
              ce.width.baseVal.value = cw + (cx - m.e);

              var re = svg.rects.labour;
              var rx = re.x.baseVal.value;
              var rw = re.width.baseVal.value;
              re.x.baseVal.value = m.e;
              re.width.baseVal.value = rw + (rx - m.e);

              svg.form.recalculate();
            };

            var aepp = function () {
              var svg = this.ownerSVGElement;
              var m = this.transform.baseVal.getItem(0).matrix;

              var re = svg.rects.engineering;
              var rx = re.x.baseVal.value;
              var rw = re.width.baseVal.value;
              re.x.baseVal.value = m.e;
              re.width.baseVal.value = rw + (rx - m.e);

              svg.form.recalculate();
            };

            var mlpp = function () {
              var svg = this.ownerSVGElement;
              var m = this.transform.baseVal.getItem(0).matrix;

              var le = svg.rects.labour;
              var lx = le.x.baseVal.value;
              var lw = le.width.baseVal.value;
              le.width.baseVal.value = m.e - lx;

              svg.form.recalculate();
            };

            svg.rects = {};
            ['reference', 'design', 'engineering',
             'construction', 'labour'].map(function (id) {
               svg.rects[id] = document.getElementById(id) });
    
            svg.setScale = function (value) {
              var ref = this.rects.reference.width.baseVal.value;
              var scaleLog = Math.floor(Math.log10(value));
              var scale = Math.pow(10, scaleLog);
              var newWidth = scale / value * ref;
              var elem = document.getElementById('scale');
              elem.points.getItem(2).x = elem.points.getItem(3).x = newWidth;
              var text = document.getElementById('scale-text');
              text.x.baseVal.getItem(0).value = newWidth + 3;

              var suffix = ['', 'k', 'M', 'B', 'T'];
              var logf = Math.floor(scaleLog / 3);
              var pk   = Math.pow(10, logf * 3);

              text.firstChild.data = '$' + (scale / pk) + suffix[logf];
            };

            var load = function (e) {
              // interlink components
              svg.form = form;
              form.diagram = svg;

              // do diagram component
              [{ id: 'design-construction',              // element
                 lhs: genBoundary('architect-engineer'), // left-hand side
                 rhs: genBoundary('materials-labour'),   // right-hand side
                 pp: dcpp },                             // postprocessor
               { id: 'architect-engineer',
                 lhs: genBoundary('reference', 'x'),
                 rhs: genBoundary('design-construction'),
                 pp: aepp },
               { id: 'materials-labour',
                 lhs: genBoundary('design-construction'),
                 rhs: genBoundary('reference', 'width'),
                 pp: mlpp }].map(setupSVG);

              // reset the scale JIC
              svg.setScale(FormUtils.coerceNumber(form['prj-cost'].value));

              // do form component
              FormUtils.loadEvent(form, recalc, changeForm)(e);
            };

            window.addEventListener('load', load, false);
          })();
        </script>
        </figcaption>
      </figure>
      <p>This rigid relationship between the aspiration of usage requirements and the reality of physical material dictates the economics of every engineering project: every structure, every vehicle, every mass-produced object&#x2014;and it does so in both absolute and relative terms. The <q>highly-synthetic</q> part of the job, if it exists at all, is eclipsed completely by the conspicuous and palpable calculus of industrial-era labour and capital. Design, in the grand economic scheme of engineering projects, is a rounding error.</p>
      <blockquote class="note" id="E6PUva_VoriIBlR-zw-mcL">
        <p>If it isn't sufficiently clear: even if, in a conventional industrial project such as that illustrated above, the cost of design is <em>double</em> what was anticipated, this only represents a <var>20%</var> overrun on the entire project.</p>
      </blockquote>
      <p>As the production of meaning becomes increasingly orthogonal to the dictates of physics, an increasing fraction of the resources, devoted to a given endeavour, gets consumed by <em>design</em>. The high capital costs of <em>industrial</em> projects not only anchor the investment in design, but also mask its excesses: an overrun in design is difficult to make as massive as an overrun in construction. Moreover, the enormous cost of misallocated materials and labour in construction&#x2014;not to mention often the risk of actually <em>killing</em> people&#x2014;makes overruns in design somewhat easier to swallow. The incalculable cost of getting the design <em>wrong</em> at least partially forgives any need for extra resources to get the design <em>right</em>.</p>
      <blockquote class="note" id="EH7LpXkMz7SVehcxQLhcsK">
        <p>The business-minded will argue that even 20% is a lot, and it is, but of course the classic counter-argument is that you either pay that 20% or you lose everything, and then some.</p>
      </blockquote>
      <p>The cost of physical materials&#x2014;and the labour to work them&#x2014;fixes the order of magnitude of resources allocated to design, by itself being an order of magnitude larger. What happens when we cut that anchor loose?</p>
    </section>
    <h5>blah blah wank wank don't read past here it's not done yet</h5>
    <hr/>
    <section id="EUcYZTjYu0PiyjiYuydGqK">
      <h2>Parkinson's Law and the Fuck-it Factor</h2>
      <p>Whatever your methodological disposition, the one thing everybody who has some experience with the design process will agree upon is that design consumes arbitrarily large, contiguous chunks of human <em>attention</em>, and will consume as much as you are willing to give it. Attention is of course embedded into <em>time</em>, and so na&#xEF;vely, more designer-hours equals more design, equals <em>better</em> design&#x2014;or at least equals more <em>refined</em> design. This is not an unreasonable expectation, as long as the time allotted is <q>about enough</q> to iron out the core concerns of the thing being designed.</p>
      
      <blockquote class="note" id="EGd3bcIJ9ihKPrjqrxlmYJ">
        <p>I say <q>about enough</q> because often the people doing the design will <q>pay</q> the difference of an underfunded project by working extra hours for free. Of course, if a design project is too deeply underfunded, or simply not given enough time on the calendar&#x2014;perhaps only a little more than a few percent&#x2014;then no quantity of donated hours will save it.</p>
      </blockquote>
      <p>It is obvious when design is underfunded and/or rushed, <span class="parenthesis" title="often spectacularly">because it fails</span>. By no means, however, is a lack of time or money the <em>only</em> way a design project can fail. Successful design <em>necessarily</em> has enough money behind it&#x2014;and more importantly, enough time. The question here, is how <em>close</em> to <q>about enough</q> such resources was the project granted? In other words, how much was, for lack of a better expression, <q><em>really</em> needed</q>, and how much was <q>waste</q>?</p>
      
      <p>I scare-quote these phrases because I believe just about any designer of any kind would insist that every last jot of their work is necessary, and they wouldn't be lying. Processes adapt to available resources. <a rel="dct:references" href="https://en.wikipedia.org/wiki/Parkinson%27s_law" title="Parkinson's law &#x2014; Wikipedia">Work expands so as to fill the time available for its completion</a>. While more money can buy better equipment, hire more/better people, pay for more research, and produce more compelling presentational material, the minimum amount of <em>attention</em> a given design problem takes to solve is invariant, as design problems care neither about your burn rate, nor your production schedule.</p>
      <blockquote class="note" id="ErYVQnsytS10ovvdaSPUrK">
        <p class="quote">The bearing of a child takes nine months, no matter how many women are assigned.</p>
        <p><cite>Frederick Brooks</cite>, The Mythical Man-Month, page 17</p>
      </blockquote>
      <p>Design projects often begin as utopic hallucinations, and degenerate, in the worst cases, into harried scrambles to meet basic contractual obligations. It seems to happen at every scale. In fact, I challenge you to find one person you could call a <q>designer</q> who <em>doesn't</em> regularly  <span class="parenthesis" title="Because I want to know how they do it.">work right up to the last available minute.</span></p>
      <blockquote class="note" id="EgkqtrqH-N5ezbFbpQXJ2I">
        <p>An apt caricature of <span class="parenthesis" title="and software developers">architects and industrial designers</span> alike, is that they have such lavishly-appointed offices, because they have to sleep there.</p>
      </blockquote>
      
      <p><a rel="dct:references" href="https://youtu.be/Q1ZeXnmDZMQ?t=8m24s" title="James Kunstler: How bad architecture wrecked cities"><q><em>Fuck it</em></q> is what you say as a designer when you have run out of time.</a> Pencils down. Whatever you have right at this instant, that's what's getting shipped. The question, at this point, is <em>what</em>, exactly, is getting shipped?</p>
      <p>In design, there are the concerns which appeal to <span class="parenthesis" title="more cynically: those that coddle one's ego and impress other designers">the designer's striving for an elegant and sophisticated product</span>, those which generate a materially <em>effective</em> product, and those which satisfy the obligations of the contract. These concerns do not necessarily align.</p>
      


      <section style="display: none" id="ES5JxEzDMqjS64lQLlIUtL">
      
      
      <p>Nevertheless, every design project has a central set of interrelated concerns which are essential to the fulfillment of the <em>contract</em>, in partial overlap with <em>another</em> set of concerns which are essential to the success of the <em>product</em>&#x2014;distinct from the strictly legal obligation&#x2014;<span class="parenthesis" title="Or are they?">and the rest are just refinements.</span></p>
      
      <p>There is a horizon across which a design will satisfy the contractual obligation, and another horizon across which it will satisfy the material success of the product. Refinements, you can more or less noodle on those forever.</p>
      <p>Na&#xEF;vely, again, we might think to stack the design process in that order: first, do what you can to ensure you get <em>paid</em> instead of <em>sued</em>, and <em>then</em> worry about your long-term reputation. So-called <q>refinements</q>, grounded in neither of these concerns, are nice-to-haves, and they get whatever resources are left. Even if these targets <em>were</em> extricable from one another, arranging them too strictly in this manner is a mistake.</p>
      <p>
      </p>
      
      
      </section>
      <p>When design is an appendage of construction or manufacturing</p>
    </section>
    <section id="EDSYV_1aTrKNed-ZvrmsnK">
      <h2>A Theory of the Economics of Design</h2>
      <p>The argument implied above is that the dominating status of materials and labour in human endeavour has also dominated economic theory&#x2014;especially over the last two and a half centuries of industrialization, wherein almost all of said theory was conceived. Indeed, it wasn't until the second half of the twentieth century that treatises on design began to appear.</p>
      <p>The argument implied above is that the economic properties of the design process are poorly understood, because design is outweighed&#x2014;or at least masked&#x2014;by larger, but more well-understood costs.</p>
      <p>The symbol-generating industries, with the possible exception of Hollywood, <span class="parenthesis" title="Or at least the &#x201C;design&#x201D; is a finished product in its own right, and the industrial-era costs are decoupled, like in publishing.">have few to no industrial-era costs behind which to conceal the cost of design.</span> Design, for them, is naked and out in the open.</p>
      <blockquote class="cite" id="EuQXmyii0u6yD8ujro6cGL">
        <p>A paradoxical, but perhaps realistic, view of design goals is that their function is to motivate activity which in turn will generate new goals.</p>
        <p><cite>Herbert Simon</cite>, The Sciences of the Artificial, Third edition, p.162</p>
      </blockquote>
      <blockquote class="quote" id="ErTpx2j_M9VrdyCYj1vU_K">
        <p>Hofstadter's Law: It always takes longer than you expect, even when you take into account Hofstadter's Law.</p>
        <p><cite>Douglas Hofstadter</cite>, G&#xF6;del Escher Bach, p.152</p>
      </blockquote>
      <blockquote id="ENyjvgqboMuONq27lP7WsK">
        <p><strong class="donthyphenate">Engineering is the first derivative of just plain doing stuff. Design is the second derivative.</strong></p>
      </blockquote>

      
    </section>
    
    <section style="display: none" id="E2Wpq7gIIy7eWuPGTk0NOK">
      <h2>A Theory of the Economics of Design</h2>
      <p>When human endeavour becomes unmoored from <span class="parenthesis" title="again, and the labour to work them">the cost of materials</span>&#x2014;because there <em>aren't</em> any <q>materials</q> to speak of&#x2014;design no longer has anywhere to hide. At this point we could use a means of understanding what we're looking at. In order to do that, I first have to clarify what I mean by certain words.</p>
      <dl>
        <dt>Just Plain Doing Stuff</dt>
        <dd>This should be self-explanatory: tying your shoes, making a sandwich, laying a course of bricks. There is no deliberation in just plain doing stuff&#x2014;no economic considerations, no weighing of alternatives, no PowerPoint pitch. The goal is well-defined, the task is obvious, the capabilities have been internalized, and the resources have been allocated. <em>All</em> human activity reduces, eventually, to just plain doing stuff.</dd>
        <dt>Engineering</dt>
        <dd>
          <p>Engineering is about making things work, versus having them fail&#x2014;where <em>fail</em> is defined as exploding, collapsing, or just sitting there doing nothing. Engineering is also concerned with taking something that already <q>works</q>, and making it work more efficiently. This means that engineering primarily has to do with <em>quantities</em>: quantities of steel, concrete, fuel, velocity, tensile strength, electric charge, radioactivity, worker-hours, and inexorably, <span class="parenthesis" title="pounds, euros, yen, rubles, RMB, whatever">quantities of dollars</span>. Engineering assumes a clear objective, and its own objective is to reconcile that with reality.</p>
          <blockquote class="note" id="EME3S1ZwCczlpSbmeV_29L">
            <p>It is worth mentioning that engineering is <em>extremely</em> closely related to management. I personally consider them to be, more or less, two facets of the same discipline.</p>
          </blockquote>
        </dd>
        <dt>Design</dt>
        <dd>Design, by contrast, is about resolving gaps, conflicts, and ambiguities. That is to say design is about  <em>form</em> and <em>relation</em>. Design is also getting things to <q>work</q>, in the engineering sense, when they don't work <em>yet</em>. Design is appropriate when there is <em>not</em> a sufficiently clear objective, when the respective costs of configuration <var>A</var> and configuration <var>B</var> are roughly equivalent and what matters is their relative fitness, or otherwise to justify the allocation of additional resources in order to achieve some particular <em>qualitative</em> outcome. Design, therefore, is the act of sharpening ideas to a point, such that they can be either engineered, or <q>just done</q>.</dd>
      </dl>
      <p>These definitions may not be what we are used to; they do not match up to conventional job titles. We will see that the processes <dfn>engineering</dfn> and <dfn>design</dfn> are still compatible with the epithets <dfn>engineer</dfn> and <dfn>designer</dfn>. Indeed, through the lens of these definitions we can see that <span class="parenthesis" title="the material most often engineered being time">what designers do is mostly engineering</span>&#x2014;a claim I will elucidate in due course&#x2014;and engineers do at least <em>some</em> design. Moreover, these definitions enable us to the relate the concepts together as such:</p>

      
      
      <blockquote id="EY91daeFVPqT5xW2I-mchK">
        <p><strong class="donthyphenate">Engineering is the first derivative of just plain doing stuff. Design is the second derivative.</strong></p>
      </blockquote>
    </section>
    <section style="display: none" id="EQYvsWBFYL9S37vFeCWYXJ">
    <p><a href="math-whiz" title="Math Whiz" rel="dct:references">Calculus is not a tool I normally use</a> in my line of work. <a rel="dct:references" href="https://twitter.com/doriantaylor/status/736590338417037314">Nevertheless, I got to thinking</a>:</p>
    
    
    <h2>Ironically, This <em>is</em> Rocket Science</h2>
    <p>Information is both the material of design, <em>and</em> its product.</p>
    <p>consider the problem of building a rocket that can reach escape velocity</p>
    <p>how it behaves during launch</p>
    <p>the fuel is being ignited and ejected out the back of the rocket at a frightening rate</p>
    <p>the effect of gravity is dropping off according to the inverse square law</p>
    <p>the air resistance likewise, which means not only is there less air in the way of the rocket, there also is less and less to push against</p>
    <p>so we can see that the rocket's fuel efficiency improves dramatically as it leaves the surface of the planet.</p>
    <p>where it touches down is in the cost of materials and labour, which are ultimately linear functions, measured in kilograms and hours, which are normalized to dollars.</p>
    </section>
  </body>
</html>
