<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:media="http://search.yahoo.com/mrss/" xmlns:podcast="https://podcastindex.org/namespace/1.0">
  <channel>
    <atom:link href="https://feeds.simplecast.com/L9810DOa" rel="self" title="MP3 Audio" type="application/atom+xml"/>
    <atom:link href="https://simplecast.superfeedr.com" rel="hub" xmlns="http://www.w3.org/2005/Atom"/>
    <generator>https://simplecast.com</generator>
    <title>Signals and Threads</title>
    <description>Listen in on Jane Street’s Ron Minsky as he has conversations with engineers who are working on everything from clock synchronization to reliable multicast, build systems to reconfigurable hardware. Get a peek at how Jane Street approaches problems, and how those ideas relate to tech more broadly. You can find transcripts along with related links on our website at signalsandthreads.com.</description>
    <copyright>Jane Street</copyright>
    <language>en</language>
    <pubDate>Tue, 17 Mar 2026 17:06:13 +0000</pubDate>
    <lastBuildDate>Tue, 17 Mar 2026 17:06:24 +0000</lastBuildDate>
    <image>
      <link>https://signals-threads.simplecast.com</link>
      <title>Signals and Threads</title>
      <url>https://image.simplecastcdn.com/images/d8aba2bf-5388-42b5-a07c-479b767dfa4a/01c9b0c4-650e-4a32-bbcc-0d90437c9183/3000x3000/afd00d08-0bba-45b9-bf55-1b5afa3d2b9b.jpg?aid=rss_feed</url>
    </image>
    <link>https://signals-threads.simplecast.com</link>
    <itunes:type>episodic</itunes:type>
    <itunes:summary>Listen in on Jane Street’s Ron Minsky as he has conversations with engineers who are working on everything from clock synchronization to reliable multicast, build systems to reconfigurable hardware. Get a peek at how Jane Street approaches problems, and how those ideas relate to tech more broadly. You can find transcripts along with related links on our website at signalsandthreads.com.</itunes:summary>
    <itunes:author>Jane Street</itunes:author>
    <itunes:explicit>false</itunes:explicit>
    <itunes:image href="https://image.simplecastcdn.com/images/d8aba2bf-5388-42b5-a07c-479b767dfa4a/01c9b0c4-650e-4a32-bbcc-0d90437c9183/3000x3000/afd00d08-0bba-45b9-bf55-1b5afa3d2b9b.jpg?aid=rss_feed"/>
    <itunes:new-feed-url>https://feeds.simplecast.com/L9810DOa</itunes:new-feed-url>
    <itunes:owner>
      <itunes:name>Jane Street</itunes:name>
      <itunes:email>signals-and-threads@janestreet.com</itunes:email>
    </itunes:owner>
    <itunes:category text="Technology"/>
    <itunes:category text="Business">
      <itunes:category text="Investing"/>
    </itunes:category>
    <itunes:category text="Business">
      <itunes:category text="Careers"/>
    </itunes:category>
    <item>
      <guid isPermaLink="false">5196d591-4785-4f4c-9c7c-5b3fc7fa868b</guid>
      <title>Why Testing is Hard and How to Fix it with Will Wilson</title>
      <description><![CDATA[<p>Will Wilson is the founder and CEO of Antithesis, which is trying to change how people test software. The idea is that you run your application inside a special hypervisor environment that intelligently (and deterministically) explores the program’s state space, allowing you to pinpoint and replay the events leading to crashes, bugs, and violations of invariants. In this episode, he and Ron take a broad view of testing, considering not just “the unreasonable effectiveness of example-based tests” but also property-based testing, fuzzing, chaos testing, type systems, and formal methods. How do you blend these techniques to find the subtle, show-stopper bugs that will otherwise wake you up at 3am? As Will has discovered, making testing less painful is actually a tour of some of computer science’s most vexing and interesting problems.</p>
<p>You can find the transcript for this episode on our <a href="https://signalsandthreads.com/why-testing-is-hard-and-how-to-fix-it" target="_blank" rel="noopener noreferrer">website</a>.</p>
<p>Some links to topics that came up in the discussion:</p>
<ul>
 <li><a href="https://antithesis.com/" rel="noopener noreferrer">Antithesis</a>, Will’s company</li>
 <li><a href="https://apple.github.io/foundationdb/testing.html" rel="noopener noreferrer">FoundationDB’s deterministic simulation framework</a></li>
 <li><a href="https://hackage.haskell.org/package/QuickCheck" rel="noopener noreferrer">QuickCheck</a> — the original Haskell property-based testing library, by Koen Claessen and John Hughes</li>
 <li><a href="https://hypothesis.readthedocs.io/" rel="noopener noreferrer">Hypothesis</a> — property-based testing for Python, created by David MacIver</li>
 <li><a href="https://www.quviq.com/" rel="noopener noreferrer">QuviQ</a> — John Hughes’ company commercializing QuickCheck, including automotive testing work</li>
 <li><a href="https://netflix.github.io/chaosmonkey/" rel="noopener noreferrer">Netflix Chaos Monkey</a></li>
 <li><a href="https://en.wikipedia.org/wiki/Goodhart%27s_law" rel="noopener noreferrer">Goodhart’s law</a> — “When a measure becomes a target, it ceases to be a good measure”</li>
 <li><a href="https://en.wikipedia.org/wiki/CAP_theorem" rel="noopener noreferrer">CAP theorem</a> — the impossibility result for distributed systems that FoundationDB claims to have in some sense violated.</li>
 <li><a href="https://en.wikipedia.org/wiki/Paxos_(computer_science)" rel="noopener noreferrer">Paxos</a> — the consensus algorithm FoundationDB reimplemented from scratch</li>
 <li><a href="https://en.wikipedia.org/wiki/Large_cardinal" rel="noopener noreferrer">Large cardinals</a>, an area Will studied before abandoning mathematics</li>
 <li><a href="https://en.wikipedia.org/wiki/Lyapunov_exponent" rel="noopener noreferrer">Lyapunov exponent</a> — measure of chaotic divergence</li>
 <li><a href="https://en.wikipedia.org/wiki/G._K._Chesterton#Chesterton's_fence" rel="noopener noreferrer">Chesterton’s fence</a></li>
 <li><a href="https://blog.sigplan.org/2021/09/14/the-story-of-the-flash-fill-feature-in-excel/" rel="noopener noreferrer">The Story of the Flash Fill Feature in Excel</a></li>
 <li><a href="https://www.anthropic.com/engineering/building-c-compiler" rel="noopener noreferrer">Building a C compiler with a team of parallel Claudes</a></li>
 <li><a href="https://scholarship.law.duke.edu/faculty_scholarship/1639/" rel="noopener noreferrer">Barak Richman, “How Community Institutions Create Economic Advantage: Jewish Diamond Merchants in New York”</a></li>
</ul>
]]></description>
      <pubDate>Tue, 17 Mar 2026 17:06:13 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signals-threads.simplecast.com/episodes/why-testing-is-hard-and-how-to-fix-it-with-will-wilson-XzqcXp7B</link>
      <content:encoded><![CDATA[<p>Will Wilson is the founder and CEO of Antithesis, which is trying to change how people test software. The idea is that you run your application inside a special hypervisor environment that intelligently (and deterministically) explores the program’s state space, allowing you to pinpoint and replay the events leading to crashes, bugs, and violations of invariants. In this episode, he and Ron take a broad view of testing, considering not just “the unreasonable effectiveness of example-based tests” but also property-based testing, fuzzing, chaos testing, type systems, and formal methods. How do you blend these techniques to find the subtle, show-stopper bugs that will otherwise wake you up at 3am? As Will has discovered, making testing less painful is actually a tour of some of computer science’s most vexing and interesting problems.</p>
<p>You can find the transcript for this episode on our <a href="https://signalsandthreads.com/why-testing-is-hard-and-how-to-fix-it" target="_blank" rel="noopener noreferrer">website</a>.</p>
<p>Some links to topics that came up in the discussion:</p>
<ul>
 <li><a href="https://antithesis.com/" rel="noopener noreferrer">Antithesis</a>, Will’s company</li>
 <li><a href="https://apple.github.io/foundationdb/testing.html" rel="noopener noreferrer">FoundationDB’s deterministic simulation framework</a></li>
 <li><a href="https://hackage.haskell.org/package/QuickCheck" rel="noopener noreferrer">QuickCheck</a> — the original Haskell property-based testing library, by Koen Claessen and John Hughes</li>
 <li><a href="https://hypothesis.readthedocs.io/" rel="noopener noreferrer">Hypothesis</a> — property-based testing for Python, created by David MacIver</li>
 <li><a href="https://www.quviq.com/" rel="noopener noreferrer">QuviQ</a> — John Hughes’ company commercializing QuickCheck, including automotive testing work</li>
 <li><a href="https://netflix.github.io/chaosmonkey/" rel="noopener noreferrer">Netflix Chaos Monkey</a></li>
 <li><a href="https://en.wikipedia.org/wiki/Goodhart%27s_law" rel="noopener noreferrer">Goodhart’s law</a> — “When a measure becomes a target, it ceases to be a good measure”</li>
 <li><a href="https://en.wikipedia.org/wiki/CAP_theorem" rel="noopener noreferrer">CAP theorem</a> — the impossibility result for distributed systems that FoundationDB claims to have in some sense violated.</li>
 <li><a href="https://en.wikipedia.org/wiki/Paxos_(computer_science)" rel="noopener noreferrer">Paxos</a> — the consensus algorithm FoundationDB reimplemented from scratch</li>
 <li><a href="https://en.wikipedia.org/wiki/Large_cardinal" rel="noopener noreferrer">Large cardinals</a>, an area Will studied before abandoning mathematics</li>
 <li><a href="https://en.wikipedia.org/wiki/Lyapunov_exponent" rel="noopener noreferrer">Lyapunov exponent</a> — measure of chaotic divergence</li>
 <li><a href="https://en.wikipedia.org/wiki/G._K._Chesterton#Chesterton's_fence" rel="noopener noreferrer">Chesterton’s fence</a></li>
 <li><a href="https://blog.sigplan.org/2021/09/14/the-story-of-the-flash-fill-feature-in-excel/" rel="noopener noreferrer">The Story of the Flash Fill Feature in Excel</a></li>
 <li><a href="https://www.anthropic.com/engineering/building-c-compiler" rel="noopener noreferrer">Building a C compiler with a team of parallel Claudes</a></li>
 <li><a href="https://scholarship.law.duke.edu/faculty_scholarship/1639/" rel="noopener noreferrer">Barak Richman, “How Community Institutions Create Economic Advantage: Jewish Diamond Merchants in New York”</a></li>
</ul>
]]></content:encoded>
      <enclosure length="104099047" type="audio/mpeg" url="https://cdn.simplecast.com/media/audio/transcoded/60c74513-f6b4-4cd9-b731-9362bc93aac5/173026e7-14f0-44e7-8362-8c1923903f77/episodes/audio/group/0a599908-e4bf-4daf-b1cd-a6cf40c5895d/group-item/b6ceedf1-3bbc-492b-b0d9-6f197f3b518a/128_default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>Why Testing is Hard and How to Fix it with Will Wilson</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>01:48:26</itunes:duration>
      <itunes:summary>Will Wilson is the founder and CEO of Antithesis, which is trying to change how people test software. The idea is that you run your application inside a special hypervisor environment that intelligently (and deterministically) explores the program’s state space, allowing you to pinpoint and replay the events leading to crashes, bugs, and violations of invariants. In this episode, he and Ron take a broad view of testing, considering not just “the unreasonable effectiveness of example-based tests” but also property-based testing, fuzzing, chaos testing, type systems, and formal methods. How do you blend these techniques to find the subtle, show-stopper bugs that will otherwise wake you up at 3am? As Will has discovered, making testing less painful is actually a tour of some of computer science’s most vexing and interesting problems.</itunes:summary>
      <itunes:subtitle>Will Wilson is the founder and CEO of Antithesis, which is trying to change how people test software. The idea is that you run your application inside a special hypervisor environment that intelligently (and deterministically) explores the program’s state space, allowing you to pinpoint and replay the events leading to crashes, bugs, and violations of invariants. In this episode, he and Ron take a broad view of testing, considering not just “the unreasonable effectiveness of example-based tests” but also property-based testing, fuzzing, chaos testing, type systems, and formal methods. How do you blend these techniques to find the subtle, show-stopper bugs that will otherwise wake you up at 3am? As Will has discovered, making testing less painful is actually a tour of some of computer science’s most vexing and interesting problems.</itunes:subtitle>
      <itunes:keywords>hypervisor, property-based testing, fuzzing</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>26</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">bbb96433-3655-4b84-b753-861792c12d3c</guid>
      <title>Why ML Needs a New Programming Language with Chris Lattner</title>
      <description><![CDATA[<p>Chris Lattner is the creator of LLVM and led the development of the Swift language at Apple. With Mojo, he’s taking another big swing: How do you make the process of getting the full power out of modern GPUs productive and fun? In this episode, Ron and Chris discuss how to design a language that’s easy to use while still providing the level of control required to write state of the art kernels. A key idea is to ask programmers to fully reckon with the details of the hardware, but making that work manageable and shareable via a form of type-safe metaprogramming. The aim is to support both specialization to the computation in question as well as to the hardware platform. “Somebody has to do this work,” Chris says, “if we ever want to get to an ecosystem where one vendor doesn’t control everything.”</p><p>You can find the transcript for this episode on our <a href="https://signalsandthreads.com/why-ml-needs-a-new-programming-language" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li><a href="https://www.modular.com/blog/democratizing-compute-part-1-deepseeks-impact-on-ai">Democratizing AI compute</a> (an 11-part series)</li><li><a href="https://www.modular.com/">Modular AI</a></li><li><a href="https://www.modular.com/mojo">Mojo</a></li><li><a href="https://mlir.llvm.org/">MLIR</a></li><li><a href="https://www.swift.org/">Swift</a></li></ul>
]]></description>
      <pubDate>Wed, 3 Sep 2025 20:51:15 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signals-threads.simplecast.com/episodes/why-ml-needs-a-new-programming-language-with-chris-lattner-KAEYra_E</link>
      <content:encoded><![CDATA[<p>Chris Lattner is the creator of LLVM and led the development of the Swift language at Apple. With Mojo, he’s taking another big swing: How do you make the process of getting the full power out of modern GPUs productive and fun? In this episode, Ron and Chris discuss how to design a language that’s easy to use while still providing the level of control required to write state of the art kernels. A key idea is to ask programmers to fully reckon with the details of the hardware, but making that work manageable and shareable via a form of type-safe metaprogramming. The aim is to support both specialization to the computation in question as well as to the hardware platform. “Somebody has to do this work,” Chris says, “if we ever want to get to an ecosystem where one vendor doesn’t control everything.”</p><p>You can find the transcript for this episode on our <a href="https://signalsandthreads.com/why-ml-needs-a-new-programming-language" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li><a href="https://www.modular.com/blog/democratizing-compute-part-1-deepseeks-impact-on-ai">Democratizing AI compute</a> (an 11-part series)</li><li><a href="https://www.modular.com/">Modular AI</a></li><li><a href="https://www.modular.com/mojo">Mojo</a></li><li><a href="https://mlir.llvm.org/">MLIR</a></li><li><a href="https://www.swift.org/">Swift</a></li></ul>
]]></content:encoded>
      <enclosure length="70048401" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/837f2c41-c663-42c0-a9b4-9031484d9b8d/audio/5f33ca32-5c55-434f-8718-0f33770db9cc/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>Why ML Needs a New Programming Language with Chris Lattner</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>01:12:57</itunes:duration>
      <itunes:summary>Chris Lattner is the creator of LLVM and led the development of the Swift language at Apple. With Mojo, he’s taking another big swing: How do you make the process of getting the full power out of modern GPUs productive and fun? In this episode, Ron and Chris discuss how to design a language that’s easy to use while still providing the level of control required to write state of the art kernels. A key idea is to ask programmers to fully reckon with the details of the hardware, but making that work manageable and shareable via a form of type-safe metaprogramming. The aim is to support both specialization to the computation in question as well as to the hardware platform. “Somebody has to do this work,” Chris says, “if we ever want to get to an ecosystem where one vendor doesn’t control everything.”</itunes:summary>
      <itunes:subtitle>Chris Lattner is the creator of LLVM and led the development of the Swift language at Apple. With Mojo, he’s taking another big swing: How do you make the process of getting the full power out of modern GPUs productive and fun? In this episode, Ron and Chris discuss how to design a language that’s easy to use while still providing the level of control required to write state of the art kernels. A key idea is to ask programmers to fully reckon with the details of the hardware, but making that work manageable and shareable via a form of type-safe metaprogramming. The aim is to support both specialization to the computation in question as well as to the hardware platform. “Somebody has to do this work,” Chris says, “if we ever want to get to an ecosystem where one vendor doesn’t control everything.”</itunes:subtitle>
      <itunes:keywords>template metaprogramming, simd, modular ai, pattern matching, ai accelerators, mojo, cuda, llvm, gpu, pytorch, tensor core</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>25</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">99b2f5d6-adda-48c9-86ea-9ab5e4734b58</guid>
      <title>The Thermodynamics of Trading with Daniel Pontecorvo</title>
      <description><![CDATA[<p>Daniel Pontecorvo runs the “physical engineering” team at Jane Street. This group blends architecture, mechanical engineering, electrical engineering, and construction management to build functional physical spaces. In this episode, Ron and Dan go deep on the challenge of heat exchange in a datacenter, especially in the face of increasingly dense power demands—and the analogous problem of keeping traders cool at their desks. Along the way they discuss the way ML is changing the physical constraints of computing; the benefits of having physical engineering expertise in-house; the importance of monitoring; and whether you really need Apollo-style CO2 scrubbers to ensure your office gets fresh air.</p><p>You can find the transcript for this episode on our <a href="https://signalsandthreads.com/the-thermodynamics-of-trading" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li><a href="https://www.ashrae.org/">ASHRAE</a> (American Society of Heating, Refrigerating and Air-Conditioning Engineers)</li><li>Some <a href="https://ehp.niehs.nih.gov/doi/10.1289/ehp.1510037">research</a> <a href="https://www.researchgate.net/publication/283944378_Effects_of_Exposure_to_Carbon_Dioxide_and_Human_Bioeffluents_on_Cognitive_Performance">on</a> <a href="https://pmc.ncbi.nlm.nih.gov/articles/PMC3548274/">CO2’s effects</a> on human performance, which motivated us to look into <a href="https://en.wikipedia.org/wiki/Carbon_dioxide_scrubber">CO2 Scrubbers</a></li><li>The <a href="https://www.opencompute.org/">Open Compute Project</a></li><li><a href="https://developer.nvidia.com/blog/doubling-all2all-performance-with-nvidia-collective-communication-library-2-12/">Rail-Optimized</a> and <a href="https://people.csail.mit.edu/ghobadi/papers/rail_llm_hotnets_2023.pdf">Rail-only</a> network topologies.</li><li><a href="https://en.wikipedia.org/wiki/Immersion_cooling">Immersion cooling</a>, where you submerge a machine in a dielectric fluid!</li></ul>
]]></description>
      <pubDate>Fri, 25 Jul 2025 18:21:50 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signals-threads.simplecast.com/episodes/the-thermodynamics-of-trading-with-daniel-pontecorvo-75ib8seg</link>
      <content:encoded><![CDATA[<p>Daniel Pontecorvo runs the “physical engineering” team at Jane Street. This group blends architecture, mechanical engineering, electrical engineering, and construction management to build functional physical spaces. In this episode, Ron and Dan go deep on the challenge of heat exchange in a datacenter, especially in the face of increasingly dense power demands—and the analogous problem of keeping traders cool at their desks. Along the way they discuss the way ML is changing the physical constraints of computing; the benefits of having physical engineering expertise in-house; the importance of monitoring; and whether you really need Apollo-style CO2 scrubbers to ensure your office gets fresh air.</p><p>You can find the transcript for this episode on our <a href="https://signalsandthreads.com/the-thermodynamics-of-trading" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li><a href="https://www.ashrae.org/">ASHRAE</a> (American Society of Heating, Refrigerating and Air-Conditioning Engineers)</li><li>Some <a href="https://ehp.niehs.nih.gov/doi/10.1289/ehp.1510037">research</a> <a href="https://www.researchgate.net/publication/283944378_Effects_of_Exposure_to_Carbon_Dioxide_and_Human_Bioeffluents_on_Cognitive_Performance">on</a> <a href="https://pmc.ncbi.nlm.nih.gov/articles/PMC3548274/">CO2’s effects</a> on human performance, which motivated us to look into <a href="https://en.wikipedia.org/wiki/Carbon_dioxide_scrubber">CO2 Scrubbers</a></li><li>The <a href="https://www.opencompute.org/">Open Compute Project</a></li><li><a href="https://developer.nvidia.com/blog/doubling-all2all-performance-with-nvidia-collective-communication-library-2-12/">Rail-Optimized</a> and <a href="https://people.csail.mit.edu/ghobadi/papers/rail_llm_hotnets_2023.pdf">Rail-only</a> network topologies.</li><li><a href="https://en.wikipedia.org/wiki/Immersion_cooling">Immersion cooling</a>, where you submerge a machine in a dielectric fluid!</li></ul>
]]></content:encoded>
      <enclosure length="56427529" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/87e54873-8df0-4896-8f9d-c7413f40d6e3/audio/29504133-a7d5-41c7-9c47-10ed9f39608b/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>The Thermodynamics of Trading with Daniel Pontecorvo</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>00:58:46</itunes:duration>
      <itunes:summary>Daniel Pontecorvo runs the “physical engineering” team at Jane Street. This group blends architecture, mechanical engineering, electrical engineering, and construction management to build functional physical spaces. In this episode, Ron and Dan go deep on the challenge of heat exchange in a datacenter, especially in the face of increasingly dense power demands—and the analogous problem of keeping traders cool at their desks. Along the way they discuss the way ML is changing the physical constraints of computing; the benefits of having physical engineering expertise in-house; the importance of monitoring; and whether you really need Apollo-style CO2 scrubbers to ensure your office gets fresh air.</itunes:summary>
      <itunes:subtitle>Daniel Pontecorvo runs the “physical engineering” team at Jane Street. This group blends architecture, mechanical engineering, electrical engineering, and construction management to build functional physical spaces. In this episode, Ron and Dan go deep on the challenge of heat exchange in a datacenter, especially in the face of increasingly dense power demands—and the analogous problem of keeping traders cool at their desks. Along the way they discuss the way ML is changing the physical constraints of computing; the benefits of having physical engineering expertise in-house; the importance of monitoring; and whether you really need Apollo-style CO2 scrubbers to ensure your office gets fresh air.</itunes:subtitle>
      <itunes:keywords>direct liquid cooling, fire suppression, circadian rhythm lighting, δt, modular desks, crac unit, immersion cooling, hot aisle / cold aisle containment, rail optimized network, merv filters</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>24</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">ce30b1af-c774-41b4-8998-801184e0594f</guid>
      <title>Building Tools for Traders with Ian Henry</title>
      <description><![CDATA[<p>Ian Henry started his career at Warby Parker and Trello, building consumer apps for millions of users. Now he writes high-performance tools for a small set of experts on Jane Street’s options desk. In this episode, Ron and Ian explore what it’s like writing code at a company that has been “on its own parallel universe software adventure for the last twenty years.” Along the way, they go on a tour of Ian’s whimsical and sophisticated side projects—like Bauble, a playground for rendering trippy 3D shapes using signed distance functions—that have gone on to inform his work: writing typesafe frontend code for users who measure time in microseconds and prefer their UIs to be “six pixels high.”</p><p>You can find the transcript for this episode on our <a href="https://signalsandthreads.com/building-tools-for-traders" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li><a href="https://bauble.studio/">Bauble studio</a></li><li><a href="https://janet.guide/"><i>Janet for Mortals</i>, by Ian Henry</a></li><li><a href="https://blog.janestreet.com/the-joy-of-expect-tests/">What if writing tests was a joyful experience?</a> </li></ul>
]]></description>
      <pubDate>Wed, 28 May 2025 17:09:14 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signals-threads.simplecast.com/episodes/building-tools-for-traders-with-ian-henry-fIrYAjpi</link>
      <content:encoded><![CDATA[<p>Ian Henry started his career at Warby Parker and Trello, building consumer apps for millions of users. Now he writes high-performance tools for a small set of experts on Jane Street’s options desk. In this episode, Ron and Ian explore what it’s like writing code at a company that has been “on its own parallel universe software adventure for the last twenty years.” Along the way, they go on a tour of Ian’s whimsical and sophisticated side projects—like Bauble, a playground for rendering trippy 3D shapes using signed distance functions—that have gone on to inform his work: writing typesafe frontend code for users who measure time in microseconds and prefer their UIs to be “six pixels high.”</p><p>You can find the transcript for this episode on our <a href="https://signalsandthreads.com/building-tools-for-traders" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li><a href="https://bauble.studio/">Bauble studio</a></li><li><a href="https://janet.guide/"><i>Janet for Mortals</i>, by Ian Henry</a></li><li><a href="https://blog.janestreet.com/the-joy-of-expect-tests/">What if writing tests was a joyful experience?</a> </li></ul>
]]></content:encoded>
      <enclosure length="76474941" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/a78cac00-7c72-4279-91f7-1ca440f84115/audio/b4918219-ceb4-4a40-8646-b5456adb4a10/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>Building Tools for Traders with Ian Henry</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>01:19:39</itunes:duration>
      <itunes:summary>Ian Henry started his career at Warby Parker and Trello, building consumer apps for millions of users. Now he writes high-performance tools for a small set of experts on Jane Street’s options desk. In this episode, Ron and Ian explore what it’s like writing code at a company that has been “on its own parallel universe software adventure for the last twenty years.” Along the way, they go on a tour of Ian’s whimsical and sophisticated side projects—like Bauble, a playground for rendering trippy 3D shapes using signed distance functions—that have gone on to inform his work: writing typesafe frontend code for users who measure time in microseconds and prefer their UIs to be “six pixels high.”</itunes:summary>
      <itunes:subtitle>Ian Henry started his career at Warby Parker and Trello, building consumer apps for millions of users. Now he writes high-performance tools for a small set of experts on Jane Street’s options desk. In this episode, Ron and Ian explore what it’s like writing code at a company that has been “on its own parallel universe software adventure for the last twenty years.” Along the way, they go on a tour of Ian’s whimsical and sophisticated side projects—like Bauble, a playground for rendering trippy 3D shapes using signed distance functions—that have gone on to inform his work: writing typesafe frontend code for users who measure time in microseconds and prefer their UIs to be “six pixels high.”</itunes:subtitle>
      <itunes:keywords>pattern matching, sum types, signed distance functions, snapshot testing, lisp, react, ray marching, bonsai</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>23</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">71055a32-d2ed-4f29-9680-effa315124e1</guid>
      <title>Finding Signal in the Noise with In Young Cho</title>
      <description><![CDATA[<p>In Young Cho thought she was going to be a doctor but fell into a trading internship at Jane Street. Now she helps lead the research group’s efforts in machine learning. In this episode, In Young and Ron touch on the porous boundaries between trading, research, and software engineering, which require different sensibilities but are often blended in a single person. They discuss the tension between flexible research tools and robust production systems; the challenges of ML in a low-data, high-noise environment subject to frequent regime changes; and the shift from simple linear models to deep neural networks.</p><p>You can find the transcript for this episode on our <a href="https://signalsandthreads.com//finding-signal-in-the-noise/" target="_blank">website</a>.</p>
]]></description>
      <pubDate>Wed, 12 Mar 2025 14:41:48 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signals-threads.simplecast.com/episodes/finding-signal-in-the-noise-with-in-young-cho-qBmfD9v_</link>
      <content:encoded><![CDATA[<p>In Young Cho thought she was going to be a doctor but fell into a trading internship at Jane Street. Now she helps lead the research group’s efforts in machine learning. In this episode, In Young and Ron touch on the porous boundaries between trading, research, and software engineering, which require different sensibilities but are often blended in a single person. They discuss the tension between flexible research tools and robust production systems; the challenges of ML in a low-data, high-noise environment subject to frequent regime changes; and the shift from simple linear models to deep neural networks.</p><p>You can find the transcript for this episode on our <a href="https://signalsandthreads.com//finding-signal-in-the-noise/" target="_blank">website</a>.</p>
]]></content:encoded>
      <enclosure length="57371281" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/ecc587de-3a66-4fbd-b70e-b377d7ce9672/audio/33a511f7-2a4a-4214-9e7d-2bb389130229/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>Finding Signal in the Noise with In Young Cho</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>00:59:45</itunes:duration>
      <itunes:summary>In Young Cho thought she was going to be a doctor but fell into a trading internship at Jane Street. Now she helps lead the research group’s efforts in machine learning. In this episode, In Young and Ron touch on the porous boundaries between trading, research, and software engineering, which require different sensibilities but are often blended in a single person. They discuss the tension between flexible research tools and robust production systems; the challenges of ML in a low-data, high-noise environment subject to frequent regime changes; and the shift from simple linear models to deep neural networks.</itunes:summary>
      <itunes:subtitle>In Young Cho thought she was going to be a doctor but fell into a trading internship at Jane Street. Now she helps lead the research group’s efforts in machine learning. In this episode, In Young and Ron touch on the porous boundaries between trading, research, and software engineering, which require different sensibilities but are often blended in a single person. They discuss the tension between flexible research tools and robust production systems; the challenges of ML in a low-data, high-noise environment subject to frequent regime changes; and the shift from simple linear models to deep neural networks.</itunes:subtitle>
      <itunes:keywords>research, gpus, high-noise low-data regime, transfer learning, deep learning, trading internship, modeling, time series data</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>22</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">687db127-ef82-4e2f-b2a3-7fe306feb797</guid>
      <title>The Uncertain Art of Accelerating ML Models with Sylvain Gugger</title>
      <description><![CDATA[<p>Sylvain Gugger is a former math teacher who fell into machine learning via a MOOC and became an expert in the low-level performance details of neural networks. He’s now on the ML infrastructure team at Jane Street, where he helps traders speed up their models. In this episode, Sylvain and Ron go deep on learning rate schedules; the subtle performance bugs PyTorch lets you write; how to keep a hungry GPU well-fed; and lots more, including the foremost importance of reproducibility in training runs. They also discuss some of the unique challenges of doing ML in the world of trading, like the unusual size and shape of market data and the need to do inference at shockingly low latencies.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/the-uncertain-art-of-accelerating-ml-models" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li><a href="https://course.fast.ai/">“Practical Deep Learning for Coders,”</a> a FastAI MOOC by Jeremy Howard, and the <a href="https://fastai.github.io/fastbook2e/">book</a>, of which Sylvain is a co-author.</li><li>The <a href="https://dawn.cs.stanford.edu/benchmark/#cifar10-train-cost">Stanford DAWNBench</a> competition that Sylvain participated in.</li><li><a href="https://huggingface.co/">HuggingFace</a>, and the <a href="https://huggingface.co/docs/accelerate/en/index">Accelerate library</a> that Sylvain wrote there.</li><li>Some of the languages/systems for expression ML models that were discussed: <a href="https://pytorch.org/">PyTorch</a>, <a href="https://www.tensorflow.org/">TensorFlow</a>, <a href="https://github.com/jax-ml/jax">Jax</a>, <a href="https://www.modular.com/mojo">Mojo</a>, and <a href="https://triton-lang.org/main/index.html">Triton</a></li><li>CUDA <a href="https://developer.nvidia.com/blog/cuda-graphs/">graphs</a> and <a href="https://developer.download.nvidia.com/CUDA/training/StreamsAndConcurrencyWebinar.pdf">streams</a></li><li><a href="https://people.eecs.berkeley.edu/~brecht/papers/hogwildTR.pdf">Hogwild concurrency</a></li></ul>
]]></description>
      <pubDate>Mon, 14 Oct 2024 14:47:42 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signals-threads.simplecast.com/episodes/the-uncertain-art-of-accelerating-ml-models-with-sylvain-gugger-moYuL4Ps</link>
      <content:encoded><![CDATA[<p>Sylvain Gugger is a former math teacher who fell into machine learning via a MOOC and became an expert in the low-level performance details of neural networks. He’s now on the ML infrastructure team at Jane Street, where he helps traders speed up their models. In this episode, Sylvain and Ron go deep on learning rate schedules; the subtle performance bugs PyTorch lets you write; how to keep a hungry GPU well-fed; and lots more, including the foremost importance of reproducibility in training runs. They also discuss some of the unique challenges of doing ML in the world of trading, like the unusual size and shape of market data and the need to do inference at shockingly low latencies.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/the-uncertain-art-of-accelerating-ml-models" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li><a href="https://course.fast.ai/">“Practical Deep Learning for Coders,”</a> a FastAI MOOC by Jeremy Howard, and the <a href="https://fastai.github.io/fastbook2e/">book</a>, of which Sylvain is a co-author.</li><li>The <a href="https://dawn.cs.stanford.edu/benchmark/#cifar10-train-cost">Stanford DAWNBench</a> competition that Sylvain participated in.</li><li><a href="https://huggingface.co/">HuggingFace</a>, and the <a href="https://huggingface.co/docs/accelerate/en/index">Accelerate library</a> that Sylvain wrote there.</li><li>Some of the languages/systems for expression ML models that were discussed: <a href="https://pytorch.org/">PyTorch</a>, <a href="https://www.tensorflow.org/">TensorFlow</a>, <a href="https://github.com/jax-ml/jax">Jax</a>, <a href="https://www.modular.com/mojo">Mojo</a>, and <a href="https://triton-lang.org/main/index.html">Triton</a></li><li>CUDA <a href="https://developer.nvidia.com/blog/cuda-graphs/">graphs</a> and <a href="https://developer.download.nvidia.com/CUDA/training/StreamsAndConcurrencyWebinar.pdf">streams</a></li><li><a href="https://people.eecs.berkeley.edu/~brecht/papers/hogwildTR.pdf">Hogwild concurrency</a></li></ul>
]]></content:encoded>
      <enclosure length="63723842" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/a1913937-4d31-4322-881a-28c91c47d113/audio/1cc87c80-9b19-4f22-88cc-7bfa1178dcf3/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>The Uncertain Art of Accelerating ML Models with Sylvain Gugger</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>01:06:22</itunes:duration>
      <itunes:summary>Sylvain Gugger is a former math teacher who fell into machine learning via a MOOC and became an expert in the low-level performance details of neural networks. He’s now on the ML infrastructure team at Jane Street, where he helps traders speed up their models. In this episode, Sylvain and Ron go deep on learning rate schedules; the subtle performance bugs PyTorch lets you write; how to keep a hungry GPU well-fed; and lots more, including the foremost importance of reproducibility in training runs. They also discuss some of the unique challenges of doing ML in the world of trading, like the unusual size and shape of market data and the need to do inference at shockingly low latencies.</itunes:summary>
      <itunes:subtitle>Sylvain Gugger is a former math teacher who fell into machine learning via a MOOC and became an expert in the low-level performance details of neural networks. He’s now on the ML infrastructure team at Jane Street, where he helps traders speed up their models. In this episode, Sylvain and Ron go deep on learning rate schedules; the subtle performance bugs PyTorch lets you write; how to keep a hungry GPU well-fed; and lots more, including the foremost importance of reproducibility in training runs. They also discuss some of the unique challenges of doing ML in the world of trading, like the unusual size and shape of market data and the need to do inference at shockingly low latencies.</itunes:subtitle>
      <itunes:keywords>jax, gpu kernels, learning rate schedules, memory transfers, cuda, convolutions, pytorch</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>21</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">2c7edb98-1e94-45af-b932-857a235c1740</guid>
      <title>Solving Puzzles in Production with Liora Friedberg</title>
      <description><![CDATA[<p>Liora Friedberg is a Production Engineer at Jane Street with a background in economics and computer science. In this episode, Liora and Ron discuss how production engineering blends high-stakes puzzle solving with thoughtful software engineering, as the people doing support build tools to make that support less necessary. They also discuss how Jane Street uses both tabletop simulation and hands-on exercises to train Production Engineers; what skills effective Production Engineers have in common; and how to create a culture where people aren’t blamed for making costly mistakes.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/solving-puzzles-in-production" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li>More about <a href="https://www.janestreet.com/production-engineering/">production engineering</a> at Jane Street, including how to apply.</li><li>Notes on <a href="https://en.wikipedia.org/wiki/Site_reliability_engineering">Site reliability engineering</a> in the wider world.</li><li><a href="https://en.wikipedia.org/wiki/Alarm_fatigue">Alarm fatigue</a> and desensitization.</li><li>Jane Street’s <a href="https://en.wikipedia.org/wiki/S-expression">1950’s era serialization-format of choice</a>,</li><li><a href="https://keeptalkinggame.com/">Some</a> <a href="https://store.steampowered.com/app/448510/Overcooked/">games</a> that Streeters have used for training people to respond to incidents.</li></ul>
]]></description>
      <pubDate>Mon, 7 Oct 2024 15:50:40 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signals-threads.simplecast.com/episodes/solving-puzzles-in-production-with-liora-friedberg-dk6vYnK2</link>
      <content:encoded><![CDATA[<p>Liora Friedberg is a Production Engineer at Jane Street with a background in economics and computer science. In this episode, Liora and Ron discuss how production engineering blends high-stakes puzzle solving with thoughtful software engineering, as the people doing support build tools to make that support less necessary. They also discuss how Jane Street uses both tabletop simulation and hands-on exercises to train Production Engineers; what skills effective Production Engineers have in common; and how to create a culture where people aren’t blamed for making costly mistakes.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/solving-puzzles-in-production" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li>More about <a href="https://www.janestreet.com/production-engineering/">production engineering</a> at Jane Street, including how to apply.</li><li>Notes on <a href="https://en.wikipedia.org/wiki/Site_reliability_engineering">Site reliability engineering</a> in the wider world.</li><li><a href="https://en.wikipedia.org/wiki/Alarm_fatigue">Alarm fatigue</a> and desensitization.</li><li>Jane Street’s <a href="https://en.wikipedia.org/wiki/S-expression">1950’s era serialization-format of choice</a>,</li><li><a href="https://keeptalkinggame.com/">Some</a> <a href="https://store.steampowered.com/app/448510/Overcooked/">games</a> that Streeters have used for training people to respond to incidents.</li></ul>
]]></content:encoded>
      <enclosure length="51695395" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/c7e2c837-d7ec-47c0-9ee6-a4fbc93a8b9c/audio/5759055c-f0c6-4d3a-b4b1-1f8229f51790/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>Solving Puzzles in Production with Liora Friedberg</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>00:53:50</itunes:duration>
      <itunes:summary>Liora Friedberg is a Production Engineer at Jane Street with a background in economics and computer science. In this episode, Liora and Ron discuss how production engineering blends high-stakes puzzle solving with thoughtful software engineering, as the people doing support build tools to make that support less necessary. They also discuss how Jane Street uses both tabletop simulation and hands-on exercises to train Production Engineers; what skills effective Production Engineers have in common; and how to create a culture where people aren’t blamed for making costly mistakes.</itunes:summary>
      <itunes:subtitle>Liora Friedberg is a Production Engineer at Jane Street with a background in economics and computer science. In this episode, Liora and Ron discuss how production engineering blends high-stakes puzzle solving with thoughtful software engineering, as the people doing support build tools to make that support less necessary. They also discuss how Jane Street uses both tabletop simulation and hands-on exercises to train Production Engineers; what skills effective Production Engineers have in common; and how to create a culture where people aren’t blamed for making costly mistakes.</itunes:subtitle>
      <itunes:keywords>metrics-based alerting, observability, sres, production engineering, site reliability engineering</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>20</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">7fbcaaa9-5840-42df-adfc-829f7f8672da</guid>
      <title>From the Lab to the Trading Floor with Erin Murphy</title>
      <description><![CDATA[<p>Erin Murphy is Jane Street’s first UX designer, and before that, she worked at NASA’s Jet Propulsion Laboratory building user interfaces for space missions. She’s also an illustrator with her own quarterly journal. In this episode, Erin and Ron discuss the challenge of doing user-centered design in an organization where experts are used to building tools for themselves. How do you bring a command-line interface to the web without making it worse for power users? They also discuss how beauty in design is more about utility than aesthetics; what Jane Street looks for in UX candidates; and how to help engineers discover what their users really want.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/from-the-lab-to-the-trading-floor" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li>Erin’s <a href="https://www.byerinmurphy.com/">website</a> that shows off her work.</li><li>Her <a href="https://www.farfromthis.com/">quarterly journal</a> of sketches and observations.</li><li>An <a href="https://depts.washington.edu/desalum/2017/05/10/erin-murphy/">article</a> about Erin’s design work with NASA JPL.</li><li>A <a href="https://ai.jpl.nasa.gov/public/documents/papers/castano-etal-AERO2022.pdf">paper</a> that among other things talks about the user study work that Erin did at JPL.</li><li>Jane Street’s <a href="https://www.janestreet.com/join-jane-street/position/6847048002/">current UX job opening</a>.</li></ul>
]]></description>
      <pubDate>Fri, 12 Jul 2024 19:15:09 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signals-threads.simplecast.com/episodes/from-the-lab-to-the-trading-floor-with-erin-murphy-hD6GHMhc</link>
      <content:encoded><![CDATA[<p>Erin Murphy is Jane Street’s first UX designer, and before that, she worked at NASA’s Jet Propulsion Laboratory building user interfaces for space missions. She’s also an illustrator with her own quarterly journal. In this episode, Erin and Ron discuss the challenge of doing user-centered design in an organization where experts are used to building tools for themselves. How do you bring a command-line interface to the web without making it worse for power users? They also discuss how beauty in design is more about utility than aesthetics; what Jane Street looks for in UX candidates; and how to help engineers discover what their users really want.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/from-the-lab-to-the-trading-floor" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li>Erin’s <a href="https://www.byerinmurphy.com/">website</a> that shows off her work.</li><li>Her <a href="https://www.farfromthis.com/">quarterly journal</a> of sketches and observations.</li><li>An <a href="https://depts.washington.edu/desalum/2017/05/10/erin-murphy/">article</a> about Erin’s design work with NASA JPL.</li><li>A <a href="https://ai.jpl.nasa.gov/public/documents/papers/castano-etal-AERO2022.pdf">paper</a> that among other things talks about the user study work that Erin did at JPL.</li><li>Jane Street’s <a href="https://www.janestreet.com/join-jane-street/position/6847048002/">current UX job opening</a>.</li></ul>
]]></content:encoded>
      <enclosure length="61055591" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/bc46e0b6-022a-4cff-901e-b548389cf63c/audio/912091b0-d56e-413f-8929-f266fd2b5beb/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>From the Lab to the Trading Floor with Erin Murphy</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>01:03:35</itunes:duration>
      <itunes:summary>Erin Murphy is Jane Street’s first UX designer, and before that, she worked at NASA’s Jet Propulsion Laboratory building user interfaces for space missions. She’s also an illustrator with her own quarterly journal. In this episode, Erin and Ron discuss the challenge of doing user-centered design in an organization where experts are used to building tools for themselves. How do you bring a command-line interface to the web without making it worse for power users? They also discuss how beauty in design is more about utility than aesthetics; what Jane Street looks for in UX candidates; and how to help engineers discover what their users really want.</itunes:summary>
      <itunes:subtitle>Erin Murphy is Jane Street’s first UX designer, and before that, she worked at NASA’s Jet Propulsion Laboratory building user interfaces for space missions. She’s also an illustrator with her own quarterly journal. In this episode, Erin and Ron discuss the challenge of doing user-centered design in an organization where experts are used to building tools for themselves. How do you bring a command-line interface to the web without making it worse for power users? They also discuss how beauty in design is more about utility than aesthetics; what Jane Street looks for in UX candidates; and how to help engineers discover what their users really want.</itunes:subtitle>
      <itunes:keywords>design, ux, user-centered design</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>19</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">0c89860d-73e9-4d81-8fa0-147a36ea4ffd</guid>
      <title>Performance Engineering on Hard Mode with Andrew Hunter</title>
      <description><![CDATA[<p>Andrew Hunter makes code really, really fast. Before joining Jane Street, he worked for seven years at Google on multithreaded architecture, and was a tech lead for tcmalloc, Google’s world-class scalable malloc implementation. In this episode, Andrew and Ron discuss how, paradoxically, it can be easier to optimize systems at hyperscale because of the impact that even miniscule changes can have. Finding performance wins in trading systems—which operate at a smaller scale, but which have bursty, low-latency workloads—is often trickier. Andrew explains how he approaches the problem, including his favorite profiling techniques and tools for visualizing traces; the unique challenges of optimizing OCaml versus C++; and when you should and shouldn’t care about nanoseconds. They also touch on the joys of musical theater, and how to pass an interview when you’re sleep-deprived.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/performance-engineering-on-hard-mode/" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li><a href="https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/44271.pdf">“Profiling a warehouse-scale computer”</a></li><li><a href="https://github.com/janestreet/magic-trace">Magic-trace</a></li><li><a href="https://en.wikipedia.org/wiki/OODA_loop">OODA loop</a></li></ul>
]]></description>
      <pubDate>Tue, 28 Nov 2023 22:08:42 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signals-threads.simplecast.com/episodes/performance-engineering-on-hard-mode-with-andrew-hunter-fxhCMIkB</link>
      <content:encoded><![CDATA[<p>Andrew Hunter makes code really, really fast. Before joining Jane Street, he worked for seven years at Google on multithreaded architecture, and was a tech lead for tcmalloc, Google’s world-class scalable malloc implementation. In this episode, Andrew and Ron discuss how, paradoxically, it can be easier to optimize systems at hyperscale because of the impact that even miniscule changes can have. Finding performance wins in trading systems—which operate at a smaller scale, but which have bursty, low-latency workloads—is often trickier. Andrew explains how he approaches the problem, including his favorite profiling techniques and tools for visualizing traces; the unique challenges of optimizing OCaml versus C++; and when you should and shouldn’t care about nanoseconds. They also touch on the joys of musical theater, and how to pass an interview when you’re sleep-deprived.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/performance-engineering-on-hard-mode/" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li><a href="https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/44271.pdf">“Profiling a warehouse-scale computer”</a></li><li><a href="https://github.com/janestreet/magic-trace">Magic-trace</a></li><li><a href="https://en.wikipedia.org/wiki/OODA_loop">OODA loop</a></li></ul>
]]></content:encoded>
      <enclosure length="53345499" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/dd74aa9e-bd49-435f-b9e4-244f504c2245/audio/ca861882-aa91-4c3d-b8b2-18dd0132862a/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>Performance Engineering on Hard Mode with Andrew Hunter</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>00:55:34</itunes:duration>
      <itunes:summary>Andrew Hunter makes code really, really fast. Before joining Jane Street, he worked for seven years at Google on multithreaded architecture, and was a tech lead for tcmalloc, Google’s world-class scalable malloc implementation. In this episode, Andrew and Ron discuss how, paradoxically, it can be easier to optimize systems at hyperscale because of the impact that even miniscule changes can have. Finding performance wins in trading systems—which operate at a smaller scale, but which have bursty, low-latency workloads—is often trickier. Andrew explains how he approaches the problem, including his favorite profiling techniques and tools for visualizing traces; the unique challenges of optimizing OCaml versus C++; and when you should and shouldn’t care about nanoseconds. They also touch on the joys of musical theater, and how to pass an interview when you’re sleep-deprived.</itunes:summary>
      <itunes:subtitle>Andrew Hunter makes code really, really fast. Before joining Jane Street, he worked for seven years at Google on multithreaded architecture, and was a tech lead for tcmalloc, Google’s world-class scalable malloc implementation. In this episode, Andrew and Ron discuss how, paradoxically, it can be easier to optimize systems at hyperscale because of the impact that even miniscule changes can have. Finding performance wins in trading systems—which operate at a smaller scale, but which have bursty, low-latency workloads—is often trickier. Andrew explains how he approaches the problem, including his favorite profiling techniques and tools for visualizing traces; the unique challenges of optimizing OCaml versus C++; and when you should and shouldn’t care about nanoseconds. They also touch on the joys of musical theater, and how to pass an interview when you’re sleep-deprived.</itunes:subtitle>
      <itunes:keywords>performance engineering, magic-trace, pprof, perf</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>18</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">fdc93e1a-b7f4-48f1-9d29-08a311d82045</guid>
      <title>A Poet&apos;s Guide to Product Management with Peter Bogart-Johnson</title>
      <description><![CDATA[<p>Peter Bogart-Johnson was one of Jane Street’s first program managers, and helped bring the art of PMing—where that “P” variously stands for “project,” “product,” or some blend of the two—to the company at large. He’s also a poet and the editor of a literary magazine. In this episode, Peter and Ron discuss the challenge of gaining trust as an outsider: how do you teach teams a new way of doing things while preserving what’s already working? The key, Peter says, is you listen; a good PM is an anthropologist. They also discuss how paying down technical debt isn’t something you do instead of serving customers; what Jane Street looks for in PM candidates; and how to help teams coordinate in times of great change.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/a-poets-guide-to-product-management" target="_blank">website.</a></p><p>Some links to topics that came up in the discussion:</p><ul><li><a href="https://lit-magazine.blogspot.com/">LIT Magazine</a> (more recently <a href="https://www.litmagazine.org/">here</a>)</li><li><a href="https://staysaasy.com/product/2023/03/12/pm-engineers-dont-hate.html">How to be a PM that engineers don’t hate</a> and <a href="https://staysaasy.com/engineering/2023/06/18/how-to-be-an-engineer-pms-down-hate.html">How to be an engineer that PMs don’t hate</a></li></ul>
]]></description>
      <pubDate>Tue, 15 Aug 2023 13:42:13 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signals-threads.simplecast.com/episodes/a-poets-guide-to-product-management-with-peter-bogart-johnson-_sAIFzsS</link>
      <content:encoded><![CDATA[<p>Peter Bogart-Johnson was one of Jane Street’s first program managers, and helped bring the art of PMing—where that “P” variously stands for “project,” “product,” or some blend of the two—to the company at large. He’s also a poet and the editor of a literary magazine. In this episode, Peter and Ron discuss the challenge of gaining trust as an outsider: how do you teach teams a new way of doing things while preserving what’s already working? The key, Peter says, is you listen; a good PM is an anthropologist. They also discuss how paying down technical debt isn’t something you do instead of serving customers; what Jane Street looks for in PM candidates; and how to help teams coordinate in times of great change.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/a-poets-guide-to-product-management" target="_blank">website.</a></p><p>Some links to topics that came up in the discussion:</p><ul><li><a href="https://lit-magazine.blogspot.com/">LIT Magazine</a> (more recently <a href="https://www.litmagazine.org/">here</a>)</li><li><a href="https://staysaasy.com/product/2023/03/12/pm-engineers-dont-hate.html">How to be a PM that engineers don’t hate</a> and <a href="https://staysaasy.com/engineering/2023/06/18/how-to-be-an-engineer-pms-down-hate.html">How to be an engineer that PMs don’t hate</a></li></ul>
]]></content:encoded>
      <enclosure length="59792937" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/1fe67c22-fac0-4777-955d-7239520ff2c9/audio/87c6a41f-d07c-4e1e-911b-883fc2449be1/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>A Poet&apos;s Guide to Product Management with Peter Bogart-Johnson</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>01:02:17</itunes:duration>
      <itunes:summary>Peter Bogart-Johnson was one of Jane Street’s first program managers, and helped bring the art of PMing—where that “P” variously stands for “project,” “product,” or some blend of the two—to the company at large. He’s also a poet and the editor of a literary magazine. In this episode, Peter and Ron discuss the challenge of gaining trust as an outsider: how do you teach teams a new way of doing things while preserving what’s already working? The key, Peter says, is you listen; a good PM is an anthropologist. They also discuss how paying down technical debt isn’t something you do instead of serving customers; what Jane Street looks for in PM candidates; and how to help teams coordinate in times of great change.</itunes:summary>
      <itunes:subtitle>Peter Bogart-Johnson was one of Jane Street’s first program managers, and helped bring the art of PMing—where that “P” variously stands for “project,” “product,” or some blend of the two—to the company at large. He’s also a poet and the editor of a literary magazine. In this episode, Peter and Ron discuss the challenge of gaining trust as an outsider: how do you teach teams a new way of doing things while preserving what’s already working? The key, Peter says, is you listen; a good PM is an anthropologist. They also discuss how paying down technical debt isn’t something you do instead of serving customers; what Jane Street looks for in PM candidates; and how to help teams coordinate in times of great change.</itunes:subtitle>
      <itunes:keywords>product management, toil reduction sprint, technical debt, project management</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>17</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">3f2f7776-4fc5-4566-9518-7b0a7a843b62</guid>
      <title>The Future of Programming with Richard Eisenberg</title>
      <description><![CDATA[<p>Richard Eisenberg is one of the core maintainers of Haskell. He recently joined Jane Street’s Tools and Compilers team, where he hacks on the OCaml compiler. He and Ron discuss the powerful language feature that got him into PL design in the first place—dependent types—and its role in a world where AIs can (somewhat) competently write your code for you. They also discuss the differences between Haskell and OCaml; the perils of trying to make a language that works for everybody; and how best a company like Jane Street can collaborate with the open source community.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/future-of-programming" target="_blank">website.</a></p><p>Some links to topics that came up in the discussion:</p><ul><li><a href="https://wiki.haskell.org/Dependent_type">Dependent types</a></li><li><a href="https://www.haskell.org/ghc/">GHC</a></li><li><a href="https://www.janestreet.com/tech-talks/unboxed-types-for-ocaml/">Unboxed types in OCaml</a></li><li><a href="https://typeclasses.com/extensions-intro">Language extensions in Haskell</a></li></ul>
]]></description>
      <pubDate>Thu, 18 May 2023 15:15:49 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signals-threads.simplecast.com/episodes/the-future-of-programming-with-richard-eisenberg-pOktpZ_e</link>
      <content:encoded><![CDATA[<p>Richard Eisenberg is one of the core maintainers of Haskell. He recently joined Jane Street’s Tools and Compilers team, where he hacks on the OCaml compiler. He and Ron discuss the powerful language feature that got him into PL design in the first place—dependent types—and its role in a world where AIs can (somewhat) competently write your code for you. They also discuss the differences between Haskell and OCaml; the perils of trying to make a language that works for everybody; and how best a company like Jane Street can collaborate with the open source community.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/future-of-programming" target="_blank">website.</a></p><p>Some links to topics that came up in the discussion:</p><ul><li><a href="https://wiki.haskell.org/Dependent_type">Dependent types</a></li><li><a href="https://www.haskell.org/ghc/">GHC</a></li><li><a href="https://www.janestreet.com/tech-talks/unboxed-types-for-ocaml/">Unboxed types in OCaml</a></li><li><a href="https://typeclasses.com/extensions-intro">Language extensions in Haskell</a></li></ul>
]]></content:encoded>
      <enclosure length="57247106" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/e40321ed-5530-4dbd-a204-f36bddcc9e60/audio/4edf90ca-1f75-4bc1-90aa-533c1d3db7ad/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>The Future of Programming with Richard Eisenberg</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>00:59:37</itunes:duration>
      <itunes:summary>Richard Eisenberg is one of the core maintainers of Haskell. He recently joined Jane Street’s Tools and Compilers team, where he hacks on the OCaml compiler. He and Ron discuss the powerful language feature that got him into PL design in the first place—dependent types—and its role in a world where AIs can (somewhat) competently write your code for you. They also discuss the differences between Haskell and OCaml; the perils of trying to make a language that works for everybody; and how best a company like Jane Street can collaborate with the open source community.
</itunes:summary>
      <itunes:subtitle>Richard Eisenberg is one of the core maintainers of Haskell. He recently joined Jane Street’s Tools and Compilers team, where he hacks on the OCaml compiler. He and Ron discuss the powerful language feature that got him into PL design in the first place—dependent types—and its role in a world where AIs can (somewhat) competently write your code for you. They also discuss the differences between Haskell and OCaml; the perils of trying to make a language that works for everybody; and how best a company like Jane Street can collaborate with the open source community.
</itunes:subtitle>
      <itunes:keywords>unboxed types, ocaml, programming language design, dependent types, haskell, ai assistants</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>16</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">1304d0a9-a979-4663-aa1f-f5cae221c360</guid>
      <title>Swapping the Engine Out of a Moving Race Car with Ella Ehrlich</title>
      <description><![CDATA[<p>Ella Ehrlich has been a developer at Jane Street for close to a decade. During much of that time, she’s worked on Gord, one of Jane Street’s oldest and most critical systems, which is responsible for normalizing and distributing the firm’s trading data. Ella and Ron talk about how to grow and modernize a legacy system without compromising uptime, why game developers are the “musicians of software,” and some of the work Jane Street has done to try to hire a more diverse set of software engineers.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/swapping-the-engine-out-of-a-moving-race-car" target="_blank">website.</a></p><p>Some links to topics that came up in the discussion:</p><ul><li><a href="https://lol.fandom.com/wiki/Evil_Geniuses.NA">EG</a>, The League of Legends team that Ella is a huge fan of.</li><li><a href="https://kafka.apache.org/">Apache Kafka</a>, the message bus that Gord migrated to.</li><li>Some of the <a href="https://www.openfigi.com/">various</a> <a href="https://en.wikipedia.org/wiki/Reuters_Instrument_Code">sources</a> <a href="https://www.cmegroup.com/tools-information/vendorSymbol.html">of</a> <a href="https://www.isin.org/">symbology</a> you have to deal with when normalizing trading data. (Really, there are too many sources to list here!)</li><li>A list of Jane Street’s recruiting <a href="https://www.janestreet.com/join-jane-street/programs-and-events/">Programs and Events</a>, including <a href="https://www.janestreet.com/join-jane-street/programs-and-events/insight/">INSIGHT</a>, which focuses on women, and <a href="https://www.janestreet.com/join-jane-street/programs-and-events/in-focus/">IN FOCUS</a>, which focuses on historically underrepresented ethnic or racial minorities.</li></ul>
]]></description>
      <pubDate>Mon, 12 Sep 2022 20:46:54 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signals-threads.simplecast.com/episodes/swapping-the-engine-out-of-a-moving-race-car-with-ella-ehrlich-WWjYmqQI</link>
      <content:encoded><![CDATA[<p>Ella Ehrlich has been a developer at Jane Street for close to a decade. During much of that time, she’s worked on Gord, one of Jane Street’s oldest and most critical systems, which is responsible for normalizing and distributing the firm’s trading data. Ella and Ron talk about how to grow and modernize a legacy system without compromising uptime, why game developers are the “musicians of software,” and some of the work Jane Street has done to try to hire a more diverse set of software engineers.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/swapping-the-engine-out-of-a-moving-race-car" target="_blank">website.</a></p><p>Some links to topics that came up in the discussion:</p><ul><li><a href="https://lol.fandom.com/wiki/Evil_Geniuses.NA">EG</a>, The League of Legends team that Ella is a huge fan of.</li><li><a href="https://kafka.apache.org/">Apache Kafka</a>, the message bus that Gord migrated to.</li><li>Some of the <a href="https://www.openfigi.com/">various</a> <a href="https://en.wikipedia.org/wiki/Reuters_Instrument_Code">sources</a> <a href="https://www.cmegroup.com/tools-information/vendorSymbol.html">of</a> <a href="https://www.isin.org/">symbology</a> you have to deal with when normalizing trading data. (Really, there are too many sources to list here!)</li><li>A list of Jane Street’s recruiting <a href="https://www.janestreet.com/join-jane-street/programs-and-events/">Programs and Events</a>, including <a href="https://www.janestreet.com/join-jane-street/programs-and-events/insight/">INSIGHT</a>, which focuses on women, and <a href="https://www.janestreet.com/join-jane-street/programs-and-events/in-focus/">IN FOCUS</a>, which focuses on historically underrepresented ethnic or racial minorities.</li></ul>
]]></content:encoded>
      <enclosure length="58052137" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/dfe789c9-4362-4376-8721-7fbfc6d2cf41/audio/2e70d46a-075e-4f21-a591-09f5340715d8/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>Swapping the Engine Out of a Moving Race Car with Ella Ehrlich</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>01:00:28</itunes:duration>
      <itunes:summary>Ella Ehrlich has been a developer at Jane Street for close to a decade. During much of that time, she’s worked on Gord, one of Jane Street’s oldest and most critical systems, which is responsible for normalizing and distributing the firm’s trading data. Ella and Ron talk about how to grow and modernize a legacy system without compromising uptime, why game developers are the “musicians of software,” and some of the work Jane Street has done to try to hire a more diverse set of software engineers. </itunes:summary>
      <itunes:subtitle>Ella Ehrlich has been a developer at Jane Street for close to a decade. During much of that time, she’s worked on Gord, one of Jane Street’s oldest and most critical systems, which is responsible for normalizing and distributing the firm’s trading data. Ella and Ron talk about how to grow and modernize a legacy system without compromising uptime, why game developers are the “musicians of software,” and some of the work Jane Street has done to try to hire a more diverse set of software engineers. </itunes:subtitle>
      <itunes:keywords>insight, gord, ocaml, women in tech, symbology, internship, software engineering, kafka, women in stem, performance testing</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>15</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">09c1eda2-94d4-4da5-b769-686a96ecdd62</guid>
      <title>State Machine Replication, and Why You Should Care with Doug Patti</title>
      <description><![CDATA[<p>Doug Patti is a developer in Jane Street’s Client-Facing Tech team, where he works on a system called Concord that undergirds Jane Street’s client offerings. In this episode, Doug and Ron discuss how Concord, which has state-machine replication as its core abstraction, helps Jane Street achieve the reliability, scalability, and speed that the client business demands. They’ll also discuss Doug’s involvement in building a successor system called Aria, which is designed to deliver those same benefits to a much wider audience.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/state-machine-replication-and-why-you-should-care" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li>Jane Street’s <a href="https://www.janestreet.com/institutional-services/electronic-trading-platforms/">client-facing trading platforms</a></li><li>A Signals and Threads episode on <a href="https://signalsandthreads.com/multicast-and-the-markets/">market data and multicast</a> which discusses some of the history of state-machine replication in the markets.</li><li>The <a href="https://www.investopedia.com/terms/f/financial-information-exchange.asp">FIX protocol</a></li><li><a href="https://en.wikipedia.org/wiki/Multicast">UDP multicast</a></li><li><a href="https://en.wikipedia.org/wiki/Reliable_multicast#:~:text=A%20reliable%20multicast%20is%20any,as%20multi%2Dreceiver%20file%20transfer.">Reliable multicast</a></li><li><a href="https://kafka.apache.org/intro">Kafka</a></li></ul>
]]></description>
      <pubDate>Wed, 20 Apr 2022 16:00:00 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signals-threads.simplecast.com/episodes/state-machine-replication-and-why-you-should-care-with-doug-patti-ddqeDcTw</link>
      <content:encoded><![CDATA[<p>Doug Patti is a developer in Jane Street’s Client-Facing Tech team, where he works on a system called Concord that undergirds Jane Street’s client offerings. In this episode, Doug and Ron discuss how Concord, which has state-machine replication as its core abstraction, helps Jane Street achieve the reliability, scalability, and speed that the client business demands. They’ll also discuss Doug’s involvement in building a successor system called Aria, which is designed to deliver those same benefits to a much wider audience.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/state-machine-replication-and-why-you-should-care" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li>Jane Street’s <a href="https://www.janestreet.com/institutional-services/electronic-trading-platforms/">client-facing trading platforms</a></li><li>A Signals and Threads episode on <a href="https://signalsandthreads.com/multicast-and-the-markets/">market data and multicast</a> which discusses some of the history of state-machine replication in the markets.</li><li>The <a href="https://www.investopedia.com/terms/f/financial-information-exchange.asp">FIX protocol</a></li><li><a href="https://en.wikipedia.org/wiki/Multicast">UDP multicast</a></li><li><a href="https://en.wikipedia.org/wiki/Reliable_multicast#:~:text=A%20reliable%20multicast%20is%20any,as%20multi%2Dreceiver%20file%20transfer.">Reliable multicast</a></li><li><a href="https://kafka.apache.org/intro">Kafka</a></li></ul>
]]></content:encoded>
      <enclosure length="69261803" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/44e13bde-6193-48b1-8511-1e63395403eb/audio/90ff94ea-c874-4a6a-9cfb-572b4100cc85/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>State Machine Replication, and Why You Should Care with Doug Patti</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>01:12:09</itunes:duration>
      <itunes:summary>Doug Patti is a developer in Jane Street’s Client-Facing Tech team, where he works on a system called Concord that undergirds Jane Street’s client offerings. In this episode, Doug and Ron discuss how Concord, which has state-machine replication as its core abstraction, helps Jane Street achieve the reliability, scalability, and speed that the client business demands. They’ll also discuss Doug’s involvement in building a successor system called Aria, which is designed to deliver those same benefits to a much wider audience.</itunes:summary>
      <itunes:subtitle>Doug Patti is a developer in Jane Street’s Client-Facing Tech team, where he works on a system called Concord that undergirds Jane Street’s client offerings. In this episode, Doug and Ron discuss how Concord, which has state-machine replication as its core abstraction, helps Jane Street achieve the reliability, scalability, and speed that the client business demands. They’ll also discuss Doug’s involvement in building a successor system called Aria, which is designed to deliver those same benefits to a much wider audience.</itunes:subtitle>
      <itunes:keywords>paxos, marketdata, raft, blockchain, topics, fix protocol, proxy layers, node.js, high-touch flow, udp multicast, synchronous state machine, concord, ruby, kafka, rate limiting, shards, permissioning, threads, snapshots, smart contract, aria, race conditions</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>14</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">03ebcf1a-fa28-4945-8b68-f4753c8f4504</guid>
      <title>Memory Management with Stephen Dolan</title>
      <description><![CDATA[<p>Stephen Dolan works on Jane Street’s Tools and Compilers team where he focuses on the OCaml compiler. In this episode, Stephen and Ron take a trip down memory lane, discussing how to manage computer memory efficiently and safely. They consider trade-offs between reference counting and garbage collection, the surprising gains achieved by prefetching, and how new language features like local allocation and unboxed types could give OCaml users more control over their memory.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/memory-management" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li>Stephen’s command-line JSON processor, <a href="https://github.com/stedolan/jq">jq</a></li><li>Stephen’s Cambridge dissertation, <a href="https://www.cs.tufts.edu/~nr/cs257/archive/stephen-dolan/thesis.pdf">“Algebraic Subtyping”</a>, and a <a href="https://github.com/stedolan/mlsub">protoype implementation of mlsub</a>, a language based on those ideas.</li><li>A <a href="https://blog.janestreet.com/memory-allocator-showdown/">post from Stephen</a> on how to benchmark different memory allocators.</li><li>A Jane Street tech talk on <a href="https://www.janestreet.com/tech-talks/unboxed-types-for-ocaml/">“Unboxed Types for OCaml”</a>, and an <a href="https://github.com/ocaml/RFCs/blob/881b220adc1f358ab15f7743d5cd764222ab7d30/rfcs/unboxed-types.md">RFC</a> in the OCaml RFC repo.</li><li>A paper from Stephen and <a href="https://kcsrk.info/">KC Sivaramakrishnan</a> called <a href="https://kcsrk.info/papers/pldi18-memory.pdf">“Bounding Data Races in Space and Time”</a>, which is all about a new and better memory model for Multicore OCaml.</li><li>Another <a href="https://arxiv.org/pdf/2004.11663.pdf">paper</a> describing the design of OCaml’s multicore GC.</li><li>The Rust RFC for <a href="https://rust-lang.github.io/rfcs/0387-higher-ranked-trait-bounds.html">Higher-ranked trait bounds</a>.</li></ul>
]]></description>
      <pubDate>Wed, 5 Jan 2022 17:30:00 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signals-threads.simplecast.com/episodes/memory-management-with-stephen-dolan-VnWeJYgk</link>
      <content:encoded><![CDATA[<p>Stephen Dolan works on Jane Street’s Tools and Compilers team where he focuses on the OCaml compiler. In this episode, Stephen and Ron take a trip down memory lane, discussing how to manage computer memory efficiently and safely. They consider trade-offs between reference counting and garbage collection, the surprising gains achieved by prefetching, and how new language features like local allocation and unboxed types could give OCaml users more control over their memory.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/memory-management" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li>Stephen’s command-line JSON processor, <a href="https://github.com/stedolan/jq">jq</a></li><li>Stephen’s Cambridge dissertation, <a href="https://www.cs.tufts.edu/~nr/cs257/archive/stephen-dolan/thesis.pdf">“Algebraic Subtyping”</a>, and a <a href="https://github.com/stedolan/mlsub">protoype implementation of mlsub</a>, a language based on those ideas.</li><li>A <a href="https://blog.janestreet.com/memory-allocator-showdown/">post from Stephen</a> on how to benchmark different memory allocators.</li><li>A Jane Street tech talk on <a href="https://www.janestreet.com/tech-talks/unboxed-types-for-ocaml/">“Unboxed Types for OCaml”</a>, and an <a href="https://github.com/ocaml/RFCs/blob/881b220adc1f358ab15f7743d5cd764222ab7d30/rfcs/unboxed-types.md">RFC</a> in the OCaml RFC repo.</li><li>A paper from Stephen and <a href="https://kcsrk.info/">KC Sivaramakrishnan</a> called <a href="https://kcsrk.info/papers/pldi18-memory.pdf">“Bounding Data Races in Space and Time”</a>, which is all about a new and better memory model for Multicore OCaml.</li><li>Another <a href="https://arxiv.org/pdf/2004.11663.pdf">paper</a> describing the design of OCaml’s multicore GC.</li><li>The Rust RFC for <a href="https://rust-lang.github.io/rfcs/0387-higher-ranked-trait-bounds.html">Higher-ranked trait bounds</a>.</li></ul>
]]></content:encoded>
      <enclosure length="79260640" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/916f613d-5b83-4110-9a64-ab0818cc7f45/audio/7e950034-5521-4a15-a1e9-5e3d2f5b22fe/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>Memory Management with Stephen Dolan</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>01:22:34</itunes:duration>
      <itunes:summary>Stephen Dolan works on Jane Street’s Tools and Compilers team where he focuses on the OCaml compiler. In this episode, Stephen and Ron take a trip down memory lane, discussing how to manage computer memory efficiently and safely. They consider trade-offs between reference counting and garbage collection, the surprising gains achieved by prefetching, and how new language features like local allocation and unboxed types could give OCaml users more control over their memory.</itunes:summary>
      <itunes:subtitle>Stephen Dolan works on Jane Street’s Tools and Compilers team where he focuses on the OCaml compiler. In this episode, Stephen and Ron take a trip down memory lane, discussing how to manage computer memory efficiently and safely. They consider trade-offs between reference counting and garbage collection, the surprising gains achieved by prefetching, and how new language features like local allocation and unboxed types could give OCaml users more control over their memory.</itunes:subtitle>
      <itunes:keywords>struct, jq, reference counting, prefetching, smart constructors, rust, ocaml, monomorphization, go, json, haskell, mlsub, garbage collection, list.map, polymorphism, major heap, c, minor heap</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>13</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">358d8e7c-0979-4ff5-b2f6-be1c5f08a6da</guid>
      <title>What Is an Operating System? with Anil Madhavapeddy</title>
      <description><![CDATA[<p>Anil Madhavapeddy is an academic, author, engineer, entrepreneur, and OCaml aficionado. In this episode, Anil and Ron consider the evolving role of operating systems, security on the internet, and the pending arrival (at last!) of OCaml 5.0. They also discuss using Raspberry Pis to fight climate change; the programming inspiration found in British pubs and on Moroccan beaches; and the time Anil went to a party, got drunk, and woke up with a job working on the Mars Polar Lander.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/what-is-an-operating-system" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li>Ron, Anil, and Jason Hickey’s book, <a href="https://dev.realworldocaml.org/">“Real World OCaml”</a></li><li>Anil’s <a href="https://anil.recoil.org/">personal website</a> and <a href="https://scholar.google.com/citations?hl=en&user=u2nZ7F8AAAAJ&view_op=list_works&sortby=pubdate">Google Scholar page</a></li><li>The <a href="https://mirage.io/">MirageOS</a> library operating system</li><li>Cambridge University’s <a href="https://ocamllabs.io/">OCaml Labs</a></li><li>NASA’s <a href="https://mars.nasa.gov/mars-exploration/missions/polar-lander/">Mars Polar Lander</a></li><li>The <a href="https://xenproject.org/">Xen Project</a>, home to the <a href="https://xenproject.org/developers/teams/xen-hypervisor/">hypervisor</a></li><li>The <a href="https://tezos.com/">Tezos proof-of-stake blockchain</a></li><li>The <a href="https://coq.inria.fr/">Coq Proof Assistant</a> system</li></ul>
]]></description>
      <pubDate>Wed, 3 Nov 2021 16:00:00 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signals-threads.simplecast.com/episodes/what-is-an-operating-system-with-anil-madhavapeddy-q6Bgv_BW</link>
      <content:encoded><![CDATA[<p>Anil Madhavapeddy is an academic, author, engineer, entrepreneur, and OCaml aficionado. In this episode, Anil and Ron consider the evolving role of operating systems, security on the internet, and the pending arrival (at last!) of OCaml 5.0. They also discuss using Raspberry Pis to fight climate change; the programming inspiration found in British pubs and on Moroccan beaches; and the time Anil went to a party, got drunk, and woke up with a job working on the Mars Polar Lander.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/what-is-an-operating-system" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li>Ron, Anil, and Jason Hickey’s book, <a href="https://dev.realworldocaml.org/">“Real World OCaml”</a></li><li>Anil’s <a href="https://anil.recoil.org/">personal website</a> and <a href="https://scholar.google.com/citations?hl=en&user=u2nZ7F8AAAAJ&view_op=list_works&sortby=pubdate">Google Scholar page</a></li><li>The <a href="https://mirage.io/">MirageOS</a> library operating system</li><li>Cambridge University’s <a href="https://ocamllabs.io/">OCaml Labs</a></li><li>NASA’s <a href="https://mars.nasa.gov/mars-exploration/missions/polar-lander/">Mars Polar Lander</a></li><li>The <a href="https://xenproject.org/">Xen Project</a>, home to the <a href="https://xenproject.org/developers/teams/xen-hypervisor/">hypervisor</a></li><li>The <a href="https://tezos.com/">Tezos proof-of-stake blockchain</a></li><li>The <a href="https://coq.inria.fr/">Coq Proof Assistant</a> system</li></ul>
]]></content:encoded>
      <enclosure length="58737920" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/4de0fdb0-33a2-4906-b6b8-1a3312c8d737/audio/c72d11e8-66c5-47c8-a8e1-32bbd8aba0e0/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>What Is an Operating System? with Anil Madhavapeddy</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>01:01:11</itunes:duration>
      <itunes:summary>Anil Madhavapeddy is an academic, author, engineer, entrepreneur, and OCaml aficionado. In this episode, Anil and Ron consider the evolving role of operating systems, security on the internet, and the pending arrival (at last!) of OCaml 5.0. They also discuss using Raspberry Pis to fight climate change; the programming inspiration found in British pubs and on Moroccan beaches; and the time Anil went to a party, got drunk, and woke up with a job working on the Mars Polar Lander.</itunes:summary>
      <itunes:subtitle>Anil Madhavapeddy is an academic, author, engineer, entrepreneur, and OCaml aficionado. In this episode, Anil and Ron consider the evolving role of operating systems, security on the internet, and the pending arrival (at last!) of OCaml 5.0. They also discuss using Raspberry Pis to fight climate change; the programming inspiration found in British pubs and on Moroccan beaches; and the time Anil went to a party, got drunk, and woke up with a job working on the Mars Polar Lander.</itunes:subtitle>
      <itunes:keywords>grand central dispatch, multicore, merlin, iocp, openbsd, webassembly, docker, mirageos, garbage collector, xen hypervisor, multics, paravirtualization, rust, ocaml, go, lpc, reasonml, java, xensource, opam, dune, unix, c, io_uring, data race</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>12</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">a23d66a7-8119-47c2-843f-bf5b8e2516ea</guid>
      <title>Building a UI Framework with Ty Overby</title>
      <description><![CDATA[<p>Ty Overby is a programmer in Jane Street’s web platform group where he works on Bonsai, our OCaml library for building interactive browser-based UI. In this episode, Ty and Ron consider the functional approach to building user interfaces. They also discuss Ty’s programming roots in Neopets, what development features they crave on the web, the unfairly maligned CSS, and why Excel is “arguably the greatest programming language ever developed.”</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/building-a-ui-framework" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li>Jane Street’s <a href="https://opensource.janestreet.com/bonsai/">Bonsai</a> library</li><li>The 3D design system <a href="https://openscad.org/">OpenSCAD</a></li><li>Matt Keeter’s <a href="https://libfive.com/">libfive</a> design tools</li><li><a href="http://try.dot.net/">Try .NET</a> in-browser repl</li><li>Jane Street’s <a href="https://opensource.janestreet.com/incr_dom/">Incr_dom</a> library</li><li>The <a href="https://guide.elm-lang.org/architecture/">Elm Architecture</a> “pattern for architecting interactive programs”</li><li><a href="https://reactjs.org/">React</a> JavaScript library</li><li>The <a href="https://houdini.glitch.me/">Houdini</a> proposal</li><li><a href="https://svelte.dev/">Svelte</a> UI toolkit</li></ul>
]]></description>
      <pubDate>Wed, 6 Oct 2021 16:00:00 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signals-threads.simplecast.com/episodes/building-a-ui-framework-with-ty-overby-1YPs6hg_</link>
      <content:encoded><![CDATA[<p>Ty Overby is a programmer in Jane Street’s web platform group where he works on Bonsai, our OCaml library for building interactive browser-based UI. In this episode, Ty and Ron consider the functional approach to building user interfaces. They also discuss Ty’s programming roots in Neopets, what development features they crave on the web, the unfairly maligned CSS, and why Excel is “arguably the greatest programming language ever developed.”</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/building-a-ui-framework" target="_blank">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li>Jane Street’s <a href="https://opensource.janestreet.com/bonsai/">Bonsai</a> library</li><li>The 3D design system <a href="https://openscad.org/">OpenSCAD</a></li><li>Matt Keeter’s <a href="https://libfive.com/">libfive</a> design tools</li><li><a href="http://try.dot.net/">Try .NET</a> in-browser repl</li><li>Jane Street’s <a href="https://opensource.janestreet.com/incr_dom/">Incr_dom</a> library</li><li>The <a href="https://guide.elm-lang.org/architecture/">Elm Architecture</a> “pattern for architecting interactive programs”</li><li><a href="https://reactjs.org/">React</a> JavaScript library</li><li>The <a href="https://houdini.glitch.me/">Houdini</a> proposal</li><li><a href="https://svelte.dev/">Svelte</a> UI toolkit</li></ul>
]]></content:encoded>
      <enclosure length="57658496" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/f38a9a21-a8fd-4b30-a864-96e1f6389920/audio/a2771d8b-09d4-400f-9408-6456346995f0/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>Building a UI Framework with Ty Overby</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>01:00:04</itunes:duration>
      <itunes:summary>Ty Overby is a programmer in Jane Street’s web platform group where he works on Bonsai, our OCaml library for building interactive browser-based UI. In this episode, Ty and Ron consider the functional approach to building user interfaces. They also discuss Ty’s programming roots in Neopets, what development features they crave on the web, the unfairly maligned CSS, and why Excel is “arguably the greatest programming language ever developed.”</itunes:summary>
      <itunes:subtitle>Ty Overby is a programmer in Jane Street’s web platform group where he works on Bonsai, our OCaml library for building interactive browser-based UI. In this episode, Ty and Ron consider the functional approach to building user interfaces. They also discuss Ty’s programming roots in Neopets, what development features they crave on the web, the unfairly maligned CSS, and why Excel is “arguably the greatest programming language ever developed.”</itunes:subtitle>
      <itunes:keywords>libfive, web ui, google docs, state management, directed acyclic graph, openscad, houdini, blender, ui, ocaml, state machine, virtual dom, excel, css, react, composability, svelte, dom, incr_dom, elm architecture, bonsai</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>11</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">7ec76447-b92a-4256-b95a-225ab00251e1</guid>
      <title>Writing, Technically with James Somers</title>
      <description><![CDATA[<p>James Somers is Jane Street’s writer-in-residence, splitting his time between English and OCaml, and helping to push forward all sorts of efforts around knowledge-sharing at Jane Street. In this episode, James and Ron talk about the role of technical writing in an organization like Jane Street, and how engineering software relates to editing prose.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/writing-technically/">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li><a href="https://github.com/realworldocaml/mdx">mdx</a>, the modified Markdown format that supports executing OCaml code blocks</li><li>More on <a href="https://documentation.divio.com/introduction/">the 4 types of technical writing</a> that James references</li><li>Donald Knuth’s original book on <a href="https://en.wikipedia.org/wiki/Literate_programming">Literate Programming</a></li><li>More on <a href="https://www.newyorker.com/magazine/2013/01/14/structure">John McPhee’s use of KEDIT</a></li><li>Peter Seibel’s <a href="https://codersatwork.com/">Coders at Work</a></li><li>David Goodsell’s <a href="https://books.google.com/books/about/The_Machinery_of_Life.html?id=0nV-mIqPa5gC">The Machinery of Life</a></li><li>Scott Huler’s <a href="https://books.google.com/books?id=oqGUXPWbieMC">Defining the Wind</a></li></ul><p>Some of James’s writing <a href="https://blog.janestreet.com/author/jsomers/">on our tech blog</a></p>
]]></description>
      <pubDate>Wed, 1 Sep 2021 16:00:00 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signalsandthreads.com/</link>
      <content:encoded><![CDATA[<p>James Somers is Jane Street’s writer-in-residence, splitting his time between English and OCaml, and helping to push forward all sorts of efforts around knowledge-sharing at Jane Street. In this episode, James and Ron talk about the role of technical writing in an organization like Jane Street, and how engineering software relates to editing prose.</p><p>You can find the transcript for this episode  on our <a href="https://signalsandthreads.com/writing-technically/">website</a>.</p><p>Some links to topics that came up in the discussion:</p><ul><li><a href="https://github.com/realworldocaml/mdx">mdx</a>, the modified Markdown format that supports executing OCaml code blocks</li><li>More on <a href="https://documentation.divio.com/introduction/">the 4 types of technical writing</a> that James references</li><li>Donald Knuth’s original book on <a href="https://en.wikipedia.org/wiki/Literate_programming">Literate Programming</a></li><li>More on <a href="https://www.newyorker.com/magazine/2013/01/14/structure">John McPhee’s use of KEDIT</a></li><li>Peter Seibel’s <a href="https://codersatwork.com/">Coders at Work</a></li><li>David Goodsell’s <a href="https://books.google.com/books/about/The_Machinery_of_Life.html?id=0nV-mIqPa5gC">The Machinery of Life</a></li><li>Scott Huler’s <a href="https://books.google.com/books?id=oqGUXPWbieMC">Defining the Wind</a></li></ul><p>Some of James’s writing <a href="https://blog.janestreet.com/author/jsomers/">on our tech blog</a></p>
]]></content:encoded>
      <enclosure length="58520576" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/72b40a37-73d2-44d4-98c4-2e1ddbe8d503/audio/387cf624-27fc-4fc8-9581-7c1ba2c9e3ad/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>Writing, Technically with James Somers</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>01:00:58</itunes:duration>
      <itunes:summary>James Somers is Jane Street’s writer-in-residence, splitting his time between English and OCaml, and helping to push forward all sorts of efforts around knowledge-sharing at Jane Street. In this episode, James and Ron talk about the role of technical writing in an organization like Jane Street, and how engineering software relates to editing prose. </itunes:summary>
      <itunes:subtitle>James Somers is Jane Street’s writer-in-residence, splitting his time between English and OCaml, and helping to push forward all sorts of efforts around knowledge-sharing at Jane Street. In this episode, James and Ron talk about the role of technical writing in an organization like Jane Street, and how engineering software relates to editing prose. </itunes:subtitle>
      <itunes:keywords>writing, documentation, literate programming, knowledge sharing, editing, technical writing</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>10</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">e694fb97-03a7-4509-9d83-a69ae9a364d8</guid>
      <title>More Signals &amp; Threads coming soon!</title>
      <description><![CDATA[<p>Signals & Threads is back, and we have a fun season of topics lined up, including: Building better abstractions for design and user interfaces, the role of writing in a technical organization, the approach that different languages take to memory management...and more. We hope you’ll join us. The first episode drops September 1st.</p>
]]></description>
      <pubDate>Tue, 24 Aug 2021 13:36:17 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signals-threads.simplecast.com/episodes/more-signals-and-threads-coming-soon-bZXFSWKN</link>
      <content:encoded><![CDATA[<p>Signals & Threads is back, and we have a fun season of topics lined up, including: Building better abstractions for design and user interfaces, the role of writing in a technical organization, the approach that different languages take to memory management...and more. We hope you’ll join us. The first episode drops September 1st.</p>
]]></content:encoded>
      <enclosure length="578528" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/247f3f91-ad46-4cc4-bd57-f9dbcdb7a223/audio/38347740-73f2-4e54-a4ba-7f9aff13bbe3/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>More Signals &amp; Threads coming soon!</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>00:00:37</itunes:duration>
      <itunes:summary>Signals &amp; Threads is back, and we have a fun season of topics lined up, including: Building better abstractions for design and user interfaces, the role of writing in a technical organization, the approach that different languages take to memory management...and more. We hope you’ll join us. The first episode drops September 1st.</itunes:summary>
      <itunes:subtitle>Signals &amp; Threads is back, and we have a fun season of topics lined up, including: Building better abstractions for design and user interfaces, the role of writing in a technical organization, the approach that different languages take to memory management...and more. We hope you’ll join us. The first episode drops September 1st.</itunes:subtitle>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>trailer</itunes:episodeType>
    </item>
    <item>
      <guid isPermaLink="false">20f62586-b232-46c4-9f51-298c918b2385</guid>
      <title>An inside look at Jane Street&apos;s tech internship with Jeanne Van Briesen, Matt Else, and Grace Zhang</title>
      <description><![CDATA[<p>In this week's episode, the season 1 finale, Ron speaks with Jeanne, Matt, and Grace, three former tech interns at Jane Street who have returned as full-timers. They talk about the experience of being an intern at Jane Street, the types of projects that interns work on, and how they've found the transition to full-time work.</p><p>You can find the transcript for this episode along with links to things we discussed on our <a href="https://signalsandthreads.com/multicast-and-the-markets">website</a>.</p>
]]></description>
      <pubDate>Fri, 6 Nov 2020 17:00:00 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signalsandthreads.com</link>
      <content:encoded><![CDATA[<p>In this week's episode, the season 1 finale, Ron speaks with Jeanne, Matt, and Grace, three former tech interns at Jane Street who have returned as full-timers. They talk about the experience of being an intern at Jane Street, the types of projects that interns work on, and how they've found the transition to full-time work.</p><p>You can find the transcript for this episode along with links to things we discussed on our <a href="https://signalsandthreads.com/multicast-and-the-markets">website</a>.</p>
]]></content:encoded>
      <enclosure length="60346496" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/1d116f50-ddae-434f-915d-93597e2f5747/audio/e0787819-fcbf-4f70-918c-0dbeddd837f3/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>An inside look at Jane Street&apos;s tech internship with Jeanne Van Briesen, Matt Else, and Grace Zhang</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>01:02:52</itunes:duration>
      <itunes:summary>In this week&apos;s episode, the season 1 finale, Ron speaks with Jeanne, Matt, and Grace, three former tech interns at Jane Street who have returned as full-timers. They talk about the experience of being an intern at Jane Street, the types of projects that interns work on, and how they&apos;ve found the transition to full-time work.</itunes:summary>
      <itunes:subtitle>In this week&apos;s episode, the season 1 finale, Ron speaks with Jeanne, Matt, and Grace, three former tech interns at Jane Street who have returned as full-timers. They talk about the experience of being an intern at Jane Street, the types of projects that interns work on, and how they&apos;ve found the transition to full-time work.</itunes:subtitle>
      <itunes:keywords>computer science, tech recruiting, internship, onboarding, imposter syndrome, education</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>9</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">92719ac0-05fc-448a-b063-a212d196c36a</guid>
      <title>Building a functional email server with Dominick LoBraico</title>
      <description><![CDATA[<p>Despite a steady trickle of newcomers, email still reigns supreme as the chief communication mechanism for the Information Age. At Jane Street, it’s just as critical as anywhere, but there’s one difference: the system at the heart of our email infrastructure is homegrown. This week, Ron talks to Dominick LoBraico, an engineer working on Jane Street’s technology infrastructure, about how and why we built Mailcore, an email server written and configured in OCaml. They delve into questions around how best to represent the configuration of a complex system, when you should build your own and when you shouldn’t, and the benefits of bringing a code-focused approach to solving systems problems.</p><p>You can find the transcript for this episode along with links to things we discussed on our <a href="https://signalsandthreads.com/multicast-and-the-markets">website</a>.</p>
]]></description>
      <pubDate>Wed, 28 Oct 2020 16:00:00 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signalsandthreads.com</link>
      <content:encoded><![CDATA[<p>Despite a steady trickle of newcomers, email still reigns supreme as the chief communication mechanism for the Information Age. At Jane Street, it’s just as critical as anywhere, but there’s one difference: the system at the heart of our email infrastructure is homegrown. This week, Ron talks to Dominick LoBraico, an engineer working on Jane Street’s technology infrastructure, about how and why we built Mailcore, an email server written and configured in OCaml. They delve into questions around how best to represent the configuration of a complex system, when you should build your own and when you shouldn’t, and the benefits of bringing a code-focused approach to solving systems problems.</p><p>You can find the transcript for this episode along with links to things we discussed on our <a href="https://signalsandthreads.com/multicast-and-the-markets">website</a>.</p>
]]></content:encoded>
      <enclosure length="61056128" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/8ccf0f2d-6f8a-4143-b554-a0ec7266a412/audio/e8fcef07-2bf0-4be2-b96a-4fb56e105516/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>Building a functional email server with Dominick LoBraico</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>01:03:36</itunes:duration>
      <itunes:summary>Despite a steady trickle of newcomers, email still reigns supreme as the chief communication mechanism for the Information Age. At Jane Street, it’s just as critical as anywhere, but there’s one difference: the system at the heart of our email infrastructure is homegrown. This week, Ron talks to Dominick LoBraico, an engineer working on Jane Street’s technology infrastructure, about how and why we built Mailcore, an email server written and configured in OCaml. They delve into questions around how best to represent the configuration of a complex system, when you should build your own and when you shouldn’t, and the benefits of bringing a code-focused approach to solving systems problems. </itunes:summary>
      <itunes:subtitle>Despite a steady trickle of newcomers, email still reigns supreme as the chief communication mechanism for the Information Age. At Jane Street, it’s just as critical as anywhere, but there’s one difference: the system at the heart of our email infrastructure is homegrown. This week, Ron talks to Dominick LoBraico, an engineer working on Jane Street’s technology infrastructure, about how and why we built Mailcore, an email server written and configured in OCaml. They delve into questions around how best to represent the configuration of a complex system, when you should build your own and when you shouldn’t, and the benefits of bringing a code-focused approach to solving systems problems. </itunes:subtitle>
      <itunes:keywords>mailcore, systems programming, spf, configuration language, architecture, dkim, smtp, productivity hacking, dsl, email, ocaml</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>8</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">67d59160-9a9c-42a5-a5f1-f90842b140ab</guid>
      <title>Language design with Leo White</title>
      <description><![CDATA[<p>Equal parts science and art, programming language design is very much an unsolved problem. This week, Ron speaks with Leo White, from Jane Street's Tools & Compilers team, about cutting-edge language features, future work happening on OCaml, and Jane Street's relationship with the broader open-source community. The conversation covers everything from the paradox of language popularity, to advanced type system features like modular implicits and dependent types. Listen in, no programming languages PhD required!</p><p>You can find the transcript for this episode along with links to things we discussed on our <a href="https://signalsandthreads.com/multicast-and-the-markets">website</a>.</p>
]]></description>
      <pubDate>Wed, 21 Oct 2020 16:00:00 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signalsandthreads.com/language-design/</link>
      <content:encoded><![CDATA[<p>Equal parts science and art, programming language design is very much an unsolved problem. This week, Ron speaks with Leo White, from Jane Street's Tools & Compilers team, about cutting-edge language features, future work happening on OCaml, and Jane Street's relationship with the broader open-source community. The conversation covers everything from the paradox of language popularity, to advanced type system features like modular implicits and dependent types. Listen in, no programming languages PhD required!</p><p>You can find the transcript for this episode along with links to things we discussed on our <a href="https://signalsandthreads.com/multicast-and-the-markets">website</a>.</p>
]]></content:encoded>
      <enclosure length="65266304" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/991d5acb-ec74-4b8b-a64d-5474661b8ee0/audio/60b4fc9c-3e81-4fb3-a695-ae433b0ad204/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>Language design with Leo White</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>01:07:59</itunes:duration>
      <itunes:summary>Equal parts science and art, programming language design is very much an unsolved problem. This week, Ron speaks with Leo White, from Jane Street&apos;s Tools &amp; Compilers team, about cutting-edge language features, future work happening on OCaml, and Jane Street&apos;s relationship with the broader open-source community. The conversation covers everything from the paradox of language popularity, to advanced type system features like modular implicits and dependent types. Listen in, no programming languages PhD required!</itunes:summary>
      <itunes:subtitle>Equal parts science and art, programming language design is very much an unsolved problem. This week, Ron speaks with Leo White, from Jane Street&apos;s Tools &amp; Compilers team, about cutting-edge language features, future work happening on OCaml, and Jane Street&apos;s relationship with the broader open-source community. The conversation covers everything from the paradox of language popularity, to advanced type system features like modular implicits and dependent types. Listen in, no programming languages PhD required!</itunes:subtitle>
      <itunes:keywords>idris, modular implicits, compilers, algebraic effects, coq, programming languages, agda, type theory, scala, ocaml</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>7</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">294b5622-c6a5-43c6-8d7f-bdc1978b4034</guid>
      <title>Clock synchronization with Chris Perl</title>
      <description><![CDATA[<p>Clock synchronization, keeping all of the clocks on your network set to the “correct” time, sounds straightforward: our smartphones sure don’t seem to have trouble with it. Next, keep them all accurate to within 100 microseconds, and prove that you did -- now things start to get tricky. In this episode, Ron talks with Chris Perl, a systems engineer at Jane Street about the fundamental difficulty of solving this problem at scale and how we solved it.</p><p>You can find the transcript for this episode along with links to things we discussed on our <a href="https://signalsandthreads.com/multicast-and-the-markets">website</a>.</p>
]]></description>
      <pubDate>Wed, 14 Oct 2020 16:00:00 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signalsandthreads.com/clock-synchronization/</link>
      <content:encoded><![CDATA[<p>Clock synchronization, keeping all of the clocks on your network set to the “correct” time, sounds straightforward: our smartphones sure don’t seem to have trouble with it. Next, keep them all accurate to within 100 microseconds, and prove that you did -- now things start to get tricky. In this episode, Ron talks with Chris Perl, a systems engineer at Jane Street about the fundamental difficulty of solving this problem at scale and how we solved it.</p><p>You can find the transcript for this episode along with links to things we discussed on our <a href="https://signalsandthreads.com/multicast-and-the-markets">website</a>.</p>
]]></content:encoded>
      <enclosure length="42690086" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/da1b16b5-5f6d-421b-89da-5d9d45af3e11/audio/07d381e4-3f70-4419-b987-884f4893c7ee/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>Clock synchronization with Chris Perl</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>00:44:28</itunes:duration>
      <itunes:summary>Clock synchronization, keeping all of the clocks on your network set to the “correct” time, sounds straightforward: our smartphones sure don’t seem to have trouble with it. Next, keep them all accurate to within 100 microseconds, and prove that you did -- now things start to get tricky. In this episode, Ron talks with Chris Perl, a systems engineer at Jane Street about the fundamental difficulty of solving this problem at scale and how we solved it.</itunes:summary>
      <itunes:subtitle>Clock synchronization, keeping all of the clocks on your network set to the “correct” time, sounds straightforward: our smartphones sure don’t seem to have trouble with it. Next, keep them all accurate to within 100 microseconds, and prove that you did -- now things start to get tricky. In this episode, Ron talks with Chris Perl, a systems engineer at Jane Street about the fundamental difficulty of solving this problem at scale and how we solved it.</itunes:subtitle>
      <itunes:keywords>networking, linux, ptp, ntp, clock synchronization, sysadmin, unix, kernel</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>6</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">78404b97-6f38-4f73-95fd-fd57feb999b6</guid>
      <title>Python, OCaml, and Machine Learning with Laurent Mazare</title>
      <description><![CDATA[<p>A conversation with Laurent Mazare about how your choice of programming language interacts with the kind of work you do, and in particular about the tradeoffs between Python and OCaml when doing machine learning and data analysis. Ron and Laurent discuss the tradeoffs between working in a text editor and a Jupyter Notebook, the importance of visualization and interactivity, how tools and practices vary between language ecosystems, and how language features like borrow-checking in Rust and ref-counting in Swift and Python can make machine learning easier.</p><p>You can find the transcript for this episode along with links to things we discussed on our <a href="https://signalsandthreads.com/multicast-and-the-markets">website</a>.</p>
]]></description>
      <pubDate>Wed, 7 Oct 2020 16:00:00 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signalsandthreads.com/python-ocaml-and-machine-learning/</link>
      <content:encoded><![CDATA[<p>A conversation with Laurent Mazare about how your choice of programming language interacts with the kind of work you do, and in particular about the tradeoffs between Python and OCaml when doing machine learning and data analysis. Ron and Laurent discuss the tradeoffs between working in a text editor and a Jupyter Notebook, the importance of visualization and interactivity, how tools and practices vary between language ecosystems, and how language features like borrow-checking in Rust and ref-counting in Swift and Python can make machine learning easier.</p><p>You can find the transcript for this episode along with links to things we discussed on our <a href="https://signalsandthreads.com/multicast-and-the-markets">website</a>.</p>
]]></content:encoded>
      <enclosure length="57172736" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/b0aa836b-f58e-42b8-b67e-edbd1f91cc82/audio/2c7f5d59-d987-4a89-b53f-5def6ac5706a/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>Python, OCaml, and Machine Learning with Laurent Mazare</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>00:59:33</itunes:duration>
      <itunes:summary>A conversation with Laurent Mazare about how your choice of programming language interacts with the kind of work you do, and in particular about the tradeoffs between Python and OCaml when doing machine learning and data analysis. Ron and Laurent discuss the tradeoffs between working in a text editor and a Jupyter Notebook, the importance of visualization and interactivity, how tools and practices vary between language ecosystems, and how language features like borrow-checking in Rust and ref-counting in Swift and Python can make machine learning easier.</itunes:summary>
      <itunes:subtitle>A conversation with Laurent Mazare about how your choice of programming language interacts with the kind of work you do, and in particular about the tradeoffs between Python and OCaml when doing machine learning and data analysis. Ron and Laurent discuss the tradeoffs between working in a text editor and a Jupyter Notebook, the importance of visualization and interactivity, how tools and practices vary between language ecosystems, and how language features like borrow-checking in Rust and ref-counting in Swift and Python can make machine learning easier.</itunes:subtitle>
      <itunes:keywords>swift, tensorflow, rust, laurent mazare, automatic differentiation, jupyter, pytorch, ocaml</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>5</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">3d7393fa-ef87-4923-8a95-778fa2ee6249</guid>
      <title>Compiler optimization with Greta Yorsh</title>
      <description><![CDATA[<p>It’s a software engineer’s dream: A compiler that can take idiomatic high-level code and output maximally efficient instructions. Ron’s guest this week is Greta Yorsh, who has worked on just that problem in a career spanning both industry and academia. Ron and Greta talk about some  of the tricks that compilers use to make our software faster, ranging from feedback-directed optimization and super-optimization to formal analysis.</p><p>You can find the transcript for this episode along with links to things we discussed on our <a href="https://signalsandthreads.com/multicast-and-the-markets">website</a>.</p>
]]></description>
      <pubDate>Wed, 30 Sep 2020 16:00:00 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signalsandthreads.com/compiler-optimization/</link>
      <content:encoded><![CDATA[<p>It’s a software engineer’s dream: A compiler that can take idiomatic high-level code and output maximally efficient instructions. Ron’s guest this week is Greta Yorsh, who has worked on just that problem in a career spanning both industry and academia. Ron and Greta talk about some  of the tricks that compilers use to make our software faster, ranging from feedback-directed optimization and super-optimization to formal analysis.</p><p>You can find the transcript for this episode along with links to things we discussed on our <a href="https://signalsandthreads.com/multicast-and-the-markets">website</a>.</p>
]]></content:encoded>
      <enclosure length="67476149" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/2872d176-cc81-4cb9-8d13-c03cc50820e3/audio/c33d01b3-9b94-4de1-8e89-b74d680e33bc/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>Compiler optimization with Greta Yorsh</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>01:10:17</itunes:duration>
      <itunes:summary>It’s a software engineer’s dream: A compiler that can take idiomatic high-level code and output maximally efficient instructions. Ron’s guest this week is Greta Yorsh, who has worked on just that problem in a career spanning both industry and academia. Ron and Greta talk about some  of the tricks that compilers use to make our software faster, ranging from feedback-directed optimization and super-optimization to formal analysis. </itunes:summary>
      <itunes:subtitle>It’s a software engineer’s dream: A compiler that can take idiomatic high-level code and output maximally efficient instructions. Ron’s guest this week is Greta Yorsh, who has worked on just that problem in a career spanning both industry and academia. Ron and Greta talk about some  of the tricks that compilers use to make our software faster, ranging from feedback-directed optimization and super-optimization to formal analysis. </itunes:subtitle>
      <itunes:keywords>superoptimization, computer science, compiler, programming languages, jane street, performance, greta yorsh, formal verification, decidability, ocaml</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>4</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">05a5a6ea-5f07-4de3-8fa6-91a4ebb51368</guid>
      <title>Multicast and the markets with Brian Nigito</title>
      <description><![CDATA[<p>Electronic exchanges like Nasdaq need to handle a staggering number of transactions every second. To keep up, they rely on two deceptively simple-sounding concepts: single-threaded programs and multicast networking. In this episode, Ron speaks with Brian Nigito, a 20-year industry veteran who helped build some of the earliest electronic exchanges, about the tradeoffs that led to the architecture we have today, and how modern exchanges use these straightforward building blocks to achieve blindingly fast performance at scale.</p><p>You can find the transcript for this episode along with links to things we discussed on our <a href="https://signalsandthreads.com/multicast-and-the-markets">website</a>.</p>
]]></description>
      <pubDate>Wed, 23 Sep 2020 16:00:09 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signalsandthreads.com/multicast-and-the-markets/</link>
      <content:encoded><![CDATA[<p>Electronic exchanges like Nasdaq need to handle a staggering number of transactions every second. To keep up, they rely on two deceptively simple-sounding concepts: single-threaded programs and multicast networking. In this episode, Ron speaks with Brian Nigito, a 20-year industry veteran who helped build some of the earliest electronic exchanges, about the tradeoffs that led to the architecture we have today, and how modern exchanges use these straightforward building blocks to achieve blindingly fast performance at scale.</p><p>You can find the transcript for this episode along with links to things we discussed on our <a href="https://signalsandthreads.com/multicast-and-the-markets">website</a>.</p>
]]></content:encoded>
      <enclosure length="59670326" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026e7-14f0-44e7-8362-8c1923903f77/episodes/eeadbf30-90f6-444c-9981-68b636264624/audio/af8d5a0e-a5fe-41a0-8bd7-6d1b8ad42a1b/default_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>Multicast and the markets with Brian Nigito</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>01:02:09</itunes:duration>
      <itunes:summary>Electronic exchanges like Nasdaq need to handle a staggering number of transactions every second. To keep up, they rely on two deceptively simple-sounding concepts: single-threaded programs and multicast networking. In this episode, Ron speaks with Brian Nigito, a 20-year industry veteran who helped build some of the earliest electronic exchanges, about the tradeoffs that led to the architecture we have today, and how modern exchanges use these straightforward building blocks to achieve blindingly fast performance at scale.

You can find the transcript for this episode along with links to related work on our website, signalsandthreads.com.</itunes:summary>
      <itunes:subtitle>Electronic exchanges like Nasdaq need to handle a staggering number of transactions every second. To keep up, they rely on two deceptively simple-sounding concepts: single-threaded programs and multicast networking. In this episode, Ron speaks with Brian Nigito, a 20-year industry veteran who helped build some of the earliest electronic exchanges, about the tradeoffs that led to the architecture we have today, and how modern exchanges use these straightforward building blocks to achieve blindingly fast performance at scale.

You can find the transcript for this episode along with links to related work on our website, signalsandthreads.com.</itunes:subtitle>
      <itunes:keywords>networking, trading, performance, udp, multicast, exchange architecture, tcp</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>3</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">f26c302f-63ff-4982-812c-ca42e617a151</guid>
      <title>Build systems with Andrey Mokhov</title>
      <description><![CDATA[<p>Most software engineers only think about their build system when it breaks; and yet, this often unloved piece of software forms the backbone of every serious project. This week, Ron has a conversation with Andrey Mokhov about build systems, from the venerable Make to Bazel and beyond. Andrey has a lot of experience in this field, including significant contributions to <a href="https://gitlab.haskell.org/ghc/ghc/-/wikis/building/hadrian">the replacement</a> for the Glasgow Haskell Compiler’s Make-based system and <a href="https://www.cambridge.org/core/journals/journal-of-functional-programming/article/build-systems-a-la-carte-theory-and-practice/097CE52C750E69BD16B78C318754C7A4">Build Systems à la carte</a>, a paper that untangles the complex ecosystem of existing build systems. Ron and Andrey muse on questions like why every language community seems to have its own purpose-built system and, closer to home, where Andrey and the rest of the build systems team at Jane Street are focusing their efforts.</p><p>You can find the transcript for this episode along with links to related work on our <a href="https://signalsandthreads.com/build-systems">website</a>.</p>
]]></description>
      <pubDate>Wed, 16 Sep 2020 15:55:47 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signalsandthreads.com/build-systems/</link>
      <content:encoded><![CDATA[<p>Most software engineers only think about their build system when it breaks; and yet, this often unloved piece of software forms the backbone of every serious project. This week, Ron has a conversation with Andrey Mokhov about build systems, from the venerable Make to Bazel and beyond. Andrey has a lot of experience in this field, including significant contributions to <a href="https://gitlab.haskell.org/ghc/ghc/-/wikis/building/hadrian">the replacement</a> for the Glasgow Haskell Compiler’s Make-based system and <a href="https://www.cambridge.org/core/journals/journal-of-functional-programming/article/build-systems-a-la-carte-theory-and-practice/097CE52C750E69BD16B78C318754C7A4">Build Systems à la carte</a>, a paper that untangles the complex ecosystem of existing build systems. Ron and Andrey muse on questions like why every language community seems to have its own purpose-built system and, closer to home, where Andrey and the rest of the build systems team at Jane Street are focusing their efforts.</p><p>You can find the transcript for this episode along with links to related work on our <a href="https://signalsandthreads.com/build-systems">website</a>.</p>
]]></content:encoded>
      <enclosure length="55454456" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026/173026e7-14f0-44e7-8362-8c1923903f77/71b75e20-921b-457e-b41a-d96490a4c72e/amokhov-final-for-publication-v2_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>Build systems with Andrey Mokhov</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>00:57:46</itunes:duration>
      <itunes:summary>Most software engineers only think about their build system when it breaks; and yet, this often unloved piece of software forms the backbone of every serious project. This week, Ron has a conversation with Andrey Mokhov about build systems, from the venerable Make to Bazel and beyond. Andrey has a lot of experience in this field, including significant contributions to the replacement for the Glasgow Haskell Compiler’s Make-based system and Build Systems à la carte, a paper that untangles the complex ecosystem of existing build systems. Ron and Andrey muse on questions like why every language community seems to have its own purpose-built system and, closer to home, where Andrey and the rest of the build systems team at Jane Street are focusing their efforts.

You can find the transcript for this episode along with links to related work on our website, signalsandthreads.com.</itunes:summary>
      <itunes:subtitle>Most software engineers only think about their build system when it breaks; and yet, this often unloved piece of software forms the backbone of every serious project. This week, Ron has a conversation with Andrey Mokhov about build systems, from the venerable Make to Bazel and beyond. Andrey has a lot of experience in this field, including significant contributions to the replacement for the Glasgow Haskell Compiler’s Make-based system and Build Systems à la carte, a paper that untangles the complex ecosystem of existing build systems. Ron and Andrey muse on questions like why every language community seems to have its own purpose-built system and, closer to home, where Andrey and the rest of the build systems team at Jane Street are focusing their efforts.

You can find the transcript for this episode along with links to related work on our website, signalsandthreads.com.</itunes:subtitle>
      <itunes:keywords>ninja, bazel, hadrian, jane street, incremental programming, build system, make, ocaml</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>2</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">45f39868-c94e-4171-8b8e-75b5cf52d13f</guid>
      <title>Programmable hardware with Andy Ray</title>
      <description><![CDATA[<p>The ever-widening availability of FPGAs has opened the door to solving a broad set of performance-critical problems in hardware.  In this episode, Ron speaks with Andy Ray, who leads Jane Street’s hardware design team. Andy has a long career prior to Jane Street shipping hardware designs for things like modems and video codecs. That work led him to create <a href="https://github.com/janestreet/hardcaml">Hardcaml</a>, a domain-specific language for expressing hardware designs. Ron and Andy talk about the current state-of-the-art in hardware tooling, the economics of FPGAs, and how the process of designing hardware can be improved by applying lessons from software engineering.</p><p>You can find the transcript for this episode along with links to related work on our <a href="https://signalsandthreads.com/programmable-hardware/">website</a>.</p>
]]></description>
      <pubDate>Wed, 9 Sep 2020 15:17:14 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signalsandthreads.com/programmable-hardware/</link>
      <content:encoded><![CDATA[<p>The ever-widening availability of FPGAs has opened the door to solving a broad set of performance-critical problems in hardware.  In this episode, Ron speaks with Andy Ray, who leads Jane Street’s hardware design team. Andy has a long career prior to Jane Street shipping hardware designs for things like modems and video codecs. That work led him to create <a href="https://github.com/janestreet/hardcaml">Hardcaml</a>, a domain-specific language for expressing hardware designs. Ron and Andy talk about the current state-of-the-art in hardware tooling, the economics of FPGAs, and how the process of designing hardware can be improved by applying lessons from software engineering.</p><p>You can find the transcript for this episode along with links to related work on our <a href="https://signalsandthreads.com/programmable-hardware/">website</a>.</p>
]]></content:encoded>
      <enclosure length="56924798" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026/173026e7-14f0-44e7-8362-8c1923903f77/cbb985e5-5af3-40a3-aa57-2bdd7e796b33/aray-final-for-publication_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>Programmable hardware with Andy Ray</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>00:59:18</itunes:duration>
      <itunes:summary>The ever-widening availability of FPGAs has opened the door to solving a broad set of performance-critical problems in hardware.  In this episode, Ron speaks with Andy Ray, who leads Jane Street’s hardware design team. Andy has a long career prior to Jane Street shipping hardware designs for things like modems and video codecs. That work led him to create Hardcaml, a domain-specific language for expressing hardware designs. Ron and Andy talk about the current state-of-the-art in hardware tooling, the economics of FPGAs, and how the process of designing hardware can be improved by applying lessons from software engineering.

You can find the transcript for this episode along with links to related work on our website, signalsandthreads.com.</itunes:summary>
      <itunes:subtitle>The ever-widening availability of FPGAs has opened the door to solving a broad set of performance-critical problems in hardware.  In this episode, Ron speaks with Andy Ray, who leads Jane Street’s hardware design team. Andy has a long career prior to Jane Street shipping hardware designs for things like modems and video codecs. That work led him to create Hardcaml, a domain-specific language for expressing hardware designs. Ron and Andy talk about the current state-of-the-art in hardware tooling, the economics of FPGAs, and how the process of designing hardware can be improved by applying lessons from software engineering.

You can find the transcript for this episode along with links to related work on our website, signalsandthreads.com.</itunes:subtitle>
      <itunes:keywords>fpga, hardcaml, lut, asic, jane street, xilinx, andy ray, high level synthesis, ocaml</itunes:keywords>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:episode>1</itunes:episode>
    </item>
    <item>
      <guid isPermaLink="false">fe4daff7-5bb4-4c2d-9405-0ebbcb85727a</guid>
      <title>Introducing Signals &amp; Threads</title>
      <description><![CDATA[<p>Listen in on Jane Street’s Ron Minsky as he has conversations with engineers working on everything from clock synchronization to reliable multicast, build systems to reconfigurable hardware. Get a peek at how Jane Street approaches problems, and how those ideas relate to tech more broadly.</p>
]]></description>
      <pubDate>Mon, 24 Aug 2020 01:25:54 +0000</pubDate>
      <author>signals-and-threads@janestreet.com (Jane Street)</author>
      <link>https://signals-threads.simplecast.com/episodes/introducing-signals-threads-zLlapP9a</link>
      <content:encoded><![CDATA[<p>Listen in on Jane Street’s Ron Minsky as he has conversations with engineers working on everything from clock synchronization to reliable multicast, build systems to reconfigurable hardware. Get a peek at how Jane Street approaches problems, and how those ideas relate to tech more broadly.</p>
]]></content:encoded>
      <enclosure length="725291" type="audio/mpeg" url="https://cdn.simplecast.com/audio/173026/173026e7-14f0-44e7-8362-8c1923903f77/1bffb863-53cf-4234-9032-4d75330063a1/jane-street-trailer-mix-v3_tc.mp3?aid=rss_feed&amp;feed=L9810DOa"/>
      <itunes:title>Introducing Signals &amp; Threads</itunes:title>
      <itunes:author>Jane Street</itunes:author>
      <itunes:duration>00:00:45</itunes:duration>
      <itunes:summary>Listen in on Jane Street’s Ron Minsky as he has conversations with engineers working on everything from clock synchronization to reliable multicast, build systems to reconfigurable hardware. Get a peek at how Jane Street approaches problems, and how those ideas relate to tech more broadly.</itunes:summary>
      <itunes:subtitle>Listen in on Jane Street’s Ron Minsky as he has conversations with engineers working on everything from clock synchronization to reliable multicast, build systems to reconfigurable hardware. Get a peek at how Jane Street approaches problems, and how those ideas relate to tech more broadly.</itunes:subtitle>
      <itunes:explicit>false</itunes:explicit>
      <itunes:episodeType>trailer</itunes:episodeType>
    </item>
  </channel>
</rss>