<?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">Shady Derivatives and the Business of Software</title>
    <base href="https://doriantaylor.com/shady-derivatives-and-the-business-of-software"/>
    <link href="document-stats#EflDzvOfuVHEkpU0Pwb9bL" 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="Shady Derivatives and the Business of Software"/>
    <link href="lexicon/#EDk9p8qaqG0m6nxmFqAETK" rel="dct:audience" title="Digital Media Insider"/>
    <link href="person/dorian-taylor#me" rel="dct:creator" title="Dorian Taylor"/>
    <link href="lexicon/#EAdohOSM0U6cjYu1rAG22K" rel="dct:subject" title="Software Development"/>
    <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="shady-derivatives-and-the-business-of-software" datatype="xsd:token" property="ci:canonical-slug"/>
    <meta content="Financing software projects is like buying a bond. What if, instead, we thought about it like a credit default swap?" name="description" property="dct:abstract"/>
    <meta content="2013-04-18T01:08:03+00:00" datatype="xsd:dateTime" property="dct:created"/>
    <meta content="shady-derivatives-and-the-business-of-software" property="dct:identifier"/>
    <meta content="2013-04-18T01:07:13+00:00" datatype="xsd:dateTime" property="dct:issued"/>
    <meta content="2013-04-18T01:16:49+00:00" datatype="xsd:dateTime" property="dct:modified"/>
    <meta content="2013-04-20T23:41:41+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="Shady Derivatives and the Business of Software" name="twitter:title"/>
    <meta content="Financing software projects is like buying a bond. What if, instead, we thought about it like a credit default swap?" name="twitter:description"/>
    <object>
      <nav>
        <ul>
          <li>
            <a href="document-stats#EflDzvOfuVHEkpU0Pwb9bL" rev="ci:document" typeof="qb:Observation">
              <span>urn:uuid:7e50f3bc-e7ee-4547-b124-a54d0fc1bf5b</span>
            </a>
          </li>
        </ul>
      </nav>
    </object>
  </head>
  <body about="" id="ECSR5cx92KmfVktJR7GVGJ" typeof="bibo:Article">
    <blockquote id="EpdrNqs0Im4zb5rtDoNU-K">
      <p><em>October 15, 2008</em>: It was pouring rain, a deluge even by Vancouver standards. That summer, I had taken out a loan to finance a gig. The gig had gone away, but the obligation remained, and the cash had just dried up. So much for a <q>sure thing</q>.</p>
      <aside role="note" id="EU8CXX_mj_FBC562iex0wL">
        <p>Life lesson: never <em>ever</em> do that. Oh, and pedants, I asked for a line of credit but nobody would give me a reasonable one. Never take a loan when what you want is a credit line, either.</p>
      </aside>
      <p>My soon-to-be-ex-girlfriend's mother was visiting, in our tiny studio apartment, and they were bickering. In a bid to ignore them, I looked at my screen, and there was the news: the economy was officially in the toilet.</p>
      <p>It was then I had my <a href="http://en.wikiquote.org/wiki/Gone_with_the_Wind_%28film%29#Scarlett_O.27Hara" rel="dct:references">Scarlett O'Hara moment</a>: <em>never again</em>.</p>
    </blockquote>
    <p>Never again was I going to get caught in a position where far-off people making narrowly self-interested decisions could bend me over a barrel. So I set out to <em>understand</em> all that financial crap even if it killed me. What I discovered was that when you boil down the arcana and punditry, finance isn't really about money at all. Money is assumed. Instead, it's about <em>risk</em>. Or rather, tinkering with the <em>shape</em> of risk, so that your upside is way bigger than your downside, so you're more likely to win, and so your time spent exposed is shorter. And for the people that play that game, implicitly, leaving some sucker holding the bag. Having just had a major life lesson on being on the bad side of risk, I got to thinking.</p>
    <aside role="note" id="EAHPJ9OT8vRn4Jwmj_dquI">
      <p>Actually, it was <a href="http://www.interfluidity.com/" title="interfluidity" rel="dct:references">Steve Randy Waldman</a> who got me thinking, by pointing out that finance people actually trade in risk. He is sage. You should read him. But finish this first.</p>
    </aside>
    <h2><a href="http://en.wikipedia.org/wiki/The_Butter_Battle_Book" title="The Butter Battle Book &#x2014; Wikipedia" rel="dct:references">Bitsy Big-Boy Boomeroo</a></h2>
    <p>The instrument widely held to cause the most destruction of wealth and economic activity is the <a href="http://en.wikipedia.org/wiki/Credit_default_swap" title="Credit default swap &#x2014; Wikipedia" rel="dct:references">credit default swap</a>. These behave like insurance policies, wherein the policy-holder would pay the issuer on a regular schedule up to a certain maturity date. If the thing being insured&#x2014;in this case, debt&#x2014;blew up, the issuer agreed to pay the full value of the bond. Perfectly legitimate everyday activity in Finance-World, or the rest of the world: You own something, and you endeavour to protect it. But what if you didn't <em>have</em> to own it? And what if you could game the system by insuring bonds you <em>knew</em> would fail? Which is exactly what people did. Tiny downside, <em>enormous</em> upside. Peanuts if you lose, windfall if you win. And winning was almost certain.</p>
    <p>Now, I'm infamous for taking interest in atrocities, because whatever happened to cause them <em>worked</em>. If it didn't, there'd be no hugely conspicuous atrocity for everybody to gawp at. So I wanted to see if I could come up with an analogous model in my newfound armchair financier knowledge for what I actually do for a living. I came up with this:</p>
    <h2>Financing a Software Project Is Like Buying a Bond</h2>
    <p>A bond is a fixed-income instrument. You cut an enormous cheque to get a piece of paper that says at some point in the future, you will get that enormous cheque back, plus a little bit of extra money. The principal of the bond is analogous to the project's budget, the maturity date is analogous to the deadline, and the interest is analogous to the project's <acronym title="return on investment">ROI</acronym> forecast. Now, <em>what can we say about this structure</em>?</p>
    <p>Fixed downside, fixed upside, where the downside is <em>way</em> bigger than the upside. A lot to lose and <em>not</em> a lot to gain. And they <em>do</em>. Software projects are notorious for being late and going over budget, or failing completely with a humiliating whimper, just like a loan that goes into default. Even with <a href="http://agilemanifesto.org/" title="Manifesto for Agile Software Development" rel="dct:references">recent advances in development tactics</a> on the ground, this conceptualization of the project on the <em>finance</em> side means it's constantly battling to perform according to plan, against all odds. So it isn't <em>just</em> like buying a bond, <a href="https://twitter.com/kevembuangga/status/324596314505621505" rel="dct:references">it's like buying a <em>junk</em> bond</a>.</p>
    <h2>What If We Thought About It Like A <acronym title="credit default swap">CDS</acronym>?</h2>
    <p>For a credit default swap, you pay a fixed number of nominal premia on regular intervals, in the anticipation of a credit event during that period. If one happens, you get reimbursed some <em>huge</em> value in relation to your outlay. <acronym title="return on investment">ROI</acronym> isn't measured in percent, or even multiples. It's measured in <em>exponents</em>.</p>
    <p>Here, the premium would be analogous to a regular flat fee to the people working on the project. The maturity date would be analogous to some arbitrary date set for deciding if you want to continue the arrangement. The credit event is analogous to the <em>overwhelming likelihood</em> that some valuable new knowledge or capability will be discovered and implemented during that period, and the reimbursement is analogous to the arbitrary value of that event.</p>
    <p>Now, there are some differences: First, a <acronym title="credit default swap">CDS</acronym> is a <a href="https://en.wikipedia.org/wiki/Derivative_%28finance%29" title="Derivative (finance) &#x2014; Wikipedia" rel="dct:references">derivative</a>, which means it's <a href="http://en.wikipedia.org/wiki/Zero%E2%80%93sum_game" title="Zero-sum game &#x2014; Wikipedia" rel="dct:references">zero-sum</a>. In order to win, somebody has to lose. Not so with this arrangement, because we're talking about the development of new operational knowledge and capability, so you don't have to feel dirty about it. Second, the value of the upside on the discovery events is <em>arbitrary</em>, and there will be more than one. You don't know what they're going to be worth. Could be a little, could be a lot. But they will be <em>something</em>, and they will be frequent. Such is the nature of the medium. Third, the discovery events compound in value, as the results of earlier events combine with later ones.</p>
    <p>The trick is not to focus on specific outcomes but rather on <em>value</em>. Negotiate a premium that you can live with spending, with the understanding of the overwhelming probability you're going to get <em>something</em> worth more than what you spend, and that you will occasionally hit a jackpot.</p>
    <p>So the question to the <acronym title="chief financial officer">CFO</acronym> when evaluating this conceptual model for the development of new capability is: <em>how much do you wanna bet?</em></p>
  </body>
</html>
