<?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>Validation on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/validation/</link>
    <description>Recent content in Validation on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 22 Feb 2017 10:41:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/validation/index.xml" rel="self" type="application/rss+xml" />
    <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>
  </channel>
</rss>
