<?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>Clojure-in-Anger on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/series/clojure-in-anger/</link>
    <description>Recent content in Clojure-in-Anger on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 01 Mar 2018 09:44:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/series/clojure-in-anger/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Two Years of Clojure in Production: Honest Retrospective</title>
      <link>https://blog.turboawesome.win/2018/03/two-years-of-clojure-in-production-honest-retrospective/</link>
      <pubDate>Thu, 01 Mar 2018 09:44:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2018/03/two-years-of-clojure-in-production-honest-retrospective/</guid>
      <description>After two years maintaining and extending Clojure services in a financial environment, what worked, what didn&amp;#39;t, and what I&amp;#39;d carry forward.</description>
    </item>
    <item>
      <title>Persistent Data Structures Are Not Just for Functional Purists</title>
      <link>https://blog.turboawesome.win/2017/08/persistent-data-structures-are-not-just-for-functional-purists/</link>
      <pubDate>Wed, 16 Aug 2017 13:07:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2017/08/persistent-data-structures-are-not-just-for-functional-purists/</guid>
      <description>Clojure&amp;#39;s persistent data structures — immutable, structurally shared — seemed academic until we used them in a concurrent risk system. The concurrency model they enable is genuinely simpler than the lock-based alternative.</description>
    </item>
    <item>
      <title>Spec-Driven Development in Clojure: Validating Financial Data at the Edge</title>
      <link>https://blog.turboawesome.win/2017/02/spec-driven-development-in-clojure-validating-financial-data-at-the-edge/</link>
      <pubDate>Wed, 22 Feb 2017 10:41:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2017/02/spec-driven-development-in-clojure-validating-financial-data-at-the-edge/</guid>
      <description>clojure.spec was released in 2016 and changed how we thought about data validation in Clojure. For financial data where a bad field can cause a trade to execute incorrectly, spec&amp;#39;s generative testing caught bugs that normal unit tests never would.</description>
    </item>
    <item>
      <title>Clojure Data Pipelines: Transducers in Production Risk Processing</title>
      <link>https://blog.turboawesome.win/2016/11/clojure-data-pipelines-transducers-in-production-risk-processing/</link>
      <pubDate>Wed, 23 Nov 2016 13:55:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2016/11/clojure-data-pipelines-transducers-in-production-risk-processing/</guid>
      <description>Transducers are Clojure&amp;#39;s answer to pipeline composition that works without creating intermediate collections. For production data processing where allocation matters, they&amp;#39;re not a theoretical nicety — they&amp;#39;re genuinely useful.</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>
  </channel>
</rss>
