<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Risk on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/risk/</link>
    <description>Recent content in Risk on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 05 Apr 2016 14:17:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/risk/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why the Risk Team Chose Clojure (And Why It Made Sense)</title>
      <link>https://blog.turboawesome.win/2016/04/why-the-risk-team-chose-clojure-and-why-it-made-sense/</link>
      <pubDate>Tue, 05 Apr 2016 14:17:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2016/04/why-the-risk-team-chose-clojure-and-why-it-made-sense/</guid>
      <description>A Lisp in a large financial institution sounds like a punchline. The reasoning behind the decision was more principled than the stereotype suggests.</description>
    </item>
    <item>
      <title>Risk Aggregation in Real Time: Design Constraints from the Dealing Desk</title>
      <link>https://blog.turboawesome.win/2015/07/risk-aggregation-in-real-time-design-constraints-from-the-dealing-desk/</link>
      <pubDate>Wed, 08 Jul 2015 13:20:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2015/07/risk-aggregation-in-real-time-design-constraints-from-the-dealing-desk/</guid>
      <description>Aggregating live risk across thousands of positions in real time is a different problem than batch risk. The constraints from the dealing desk — sub-second freshness, continuous availability, correct arithmetic — shaped everything.</description>
    </item>
  </channel>
</rss>
