<?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>Finance on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/finance/</link>
    <description>Recent content in Finance on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 09 Jan 2019 09:04:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/finance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why I Left: On Risk, Pace, and Ownership</title>
      <link>https://blog.turboawesome.win/2019/01/why-i-left-on-risk-pace-and-ownership/</link>
      <pubDate>Wed, 09 Jan 2019 09:04:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2019/01/why-i-left-on-risk-pace-and-ownership/</guid>
      <description>After three years at a large financial institution, why I took a significant pay cut to join a tiny startup. The reasoning, the fears, and whether it was the right call.</description>
    </item>
    <item>
      <title>Event Sourcing in Financial Systems: Real Benefits, Real Costs</title>
      <link>https://blog.turboawesome.win/2018/07/event-sourcing-in-financial-systems-real-benefits-real-costs/</link>
      <pubDate>Wed, 11 Jul 2018 11:03:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2018/07/event-sourcing-in-financial-systems-real-benefits-real-costs/</guid>
      <description>Event sourcing is a natural fit for financial systems that require audit trails and point-in-time reconstruction. The costs are real too — projections, eventual consistency, and the event schema evolution problem.</description>
    </item>
    <item>
      <title>Building MiFID II Trade Reporting Infrastructure: An Engineer&#39;s View</title>
      <link>https://blog.turboawesome.win/2017/10/building-mifid-ii-trade-reporting-infrastructure-an-engineers-view/</link>
      <pubDate>Tue, 03 Oct 2017 11:45:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2017/10/building-mifid-ii-trade-reporting-infrastructure-an-engineers-view/</guid>
      <description>MiFID II required every trade to be reported within 15 minutes of execution. Building the infrastructure to meet that requirement across a large, heterogeneous estate taught us about the gap between regulatory requirements and production reality.</description>
    </item>
    <item>
      <title>Kafka in Finance: What &#39;Exactly Once&#39; Actually Costs You</title>
      <link>https://blog.turboawesome.win/2017/01/kafka-in-finance-what-exactly-once-actually-costs-you/</link>
      <pubDate>Tue, 10 Jan 2017 11:22:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2017/01/kafka-in-finance-what-exactly-once-actually-costs-you/</guid>
      <description>Kafka&amp;#39;s exactly-once semantics arrived in 0.11 with significant caveats. Using it in a regulated financial context forced a clear-eyed view of what the guarantee actually covers and what it doesn&amp;#39;t.</description>
    </item>
    <item>
      <title>KDB&#43;/Q for Java Developers: Reading the Matrix</title>
      <link>https://blog.turboawesome.win/2016/10/kdb-/q-for-java-developers-reading-the-matrix/</link>
      <pubDate>Tue, 11 Oct 2016 14:17:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2016/10/kdb-/q-for-java-developers-reading-the-matrix/</guid>
      <description>KDB&#43; is the database of choice for time-series analytics in investment banks. It&amp;#39;s fast, alien, and worth understanding. A Java developer&amp;#39;s field guide.</description>
    </item>
    <item>
      <title>Time-Series Data at a Bank: Why Relational Databases Break and What Comes Next</title>
      <link>https://blog.turboawesome.win/2016/07/time-series-data-at-a-bank-why-relational-databases-break-and-what-comes-next/</link>
      <pubDate>Wed, 06 Jul 2016 11:34:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2016/07/time-series-data-at-a-bank-why-relational-databases-break-and-what-comes-next/</guid>
      <description>Financial institutions generate millions of time-stamped data points every day. The relational database model, designed for transactional workloads, breaks down spectacularly for this use case — here&amp;#39;s why, and what replaces it.</description>
    </item>
    <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>When the Scale Changes: Moving into Institutional Finance</title>
      <link>https://blog.turboawesome.win/2016/01/when-the-scale-changes-moving-into-institutional-finance/</link>
      <pubDate>Wed, 06 Jan 2016 10:31:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2016/01/when-the-scale-changes-moving-into-institutional-finance/</guid>
      <description>Four years in a latency-obsessed trading environment, then a move to a large financial institution where the problems — and the constraints — were completely different.</description>
    </item>
    <item>
      <title>Understanding the FX Spot Market from an Engineer&#39;s Chair</title>
      <link>https://blog.turboawesome.win/2012/03/understanding-the-fx-spot-market-from-an-engineers-chair/</link>
      <pubDate>Wed, 21 Mar 2012 10:44:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2012/03/understanding-the-fx-spot-market-from-an-engineers-chair/</guid>
      <description>What actually happens when a currency is traded: the market structure, the participants, and the data flows that an engineer building FX systems needs to understand before writing a line of code.</description>
    </item>
  </channel>
</rss>
