<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" encoding="UTF-8" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:atom="http://www.w3.org/2005/Atom/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 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:fireside="http://fireside.fm/modules/rss/fireside">
  <channel>
    <fireside:hostname>web02.fireside.fm</fireside:hostname>
    <fireside:genDate>Fri, 01 May 2026 00:09:43 -0500</fireside:genDate>
    <generator>Fireside (https://fireside.fm)</generator>
    <title>Elixir Outlaws - Episodes Tagged with “Debugging”</title>
    <link>https://elixiroutlaws.com/tags/debugging</link>
    <pubDate>Thu, 22 Aug 2019 09:00:00 -0400</pubDate>
    <description>Elixir Outlaws is an informal discussion about interesting things happening in Elixir. Our goal is to capture the spirit of a conference hallway discussion in a podcast.
</description>
    <language>en-us</language>
    <itunes:type>episodic</itunes:type>
    <itunes:subtitle>The hallway track of the Elixir community</itunes:subtitle>
    <itunes:author>Elixir Outlaws</itunes:author>
    <itunes:summary>Elixir Outlaws is an informal discussion about interesting things happening in Elixir. Our goal is to capture the spirit of a conference hallway discussion in a podcast.
</itunes:summary>
    <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/4/4b3f9fe7-b118-4f29-b6ee-7baf2571b03c/cover.jpg?v=4"/>
    <itunes:explicit>no</itunes:explicit>
    <itunes:keywords>elixir, erlang, BEAM</itunes:keywords>
    <itunes:owner>
      <itunes:name>Elixir Outlaws</itunes:name>
      <itunes:email>amos@binarynoggin.com</itunes:email>
    </itunes:owner>
<itunes:category text="Technology"/>
<itunes:category text="News">
  <itunes:category text="Tech News"/>
</itunes:category>
<itunes:category text="Education">
  <itunes:category text="How To"/>
</itunes:category>
<item>
  <title>Episode 51: It's not the linux kernel drivers</title>
  <link>http://elixiroutlaws.com/51</link>
  <guid isPermaLink="false">6395aa6b-acfc-461f-b248-d2aecd10e6f5</guid>
  <pubDate>Thu, 22 Aug 2019 09:00:00 -0400</pubDate>
  <author>Elixir Outlaws</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/4b3f9fe7-b118-4f29-b6ee-7baf2571b03c/6395aa6b-acfc-461f-b248-d2aecd10e6f5.mp3" length="50894016" type="audio/mpeg"/>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>Elixir Outlaws</itunes:author>
  <itunes:subtitle>This week Chris and Amos discuss error handling, controlling overload in service calls, and tips on debugging.</itunes:subtitle>
  <itunes:duration>53:00</itunes:duration>
  <itunes:explicit>no</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/4/4b3f9fe7-b118-4f29-b6ee-7baf2571b03c/cover.jpg?v=4"/>
  <description>This week kicks off with a discussion of database indexes, Datalog, and Datomic. Amos wants to talk about error handling and when to report errors to an external service. He thinks that the goal should be to get the reported errors to zero, and Chris thinks that’s not possible. Chris explains the ways that he reports metrics and errors to collection services.
The conversation moves to circuit breakers and common patterns for handling overload in service calls.
Chris and Amos wrap up with some tips for debugging production problems with the scientific method. 
</description>
  <itunes:keywords>elixir, erlang, BEAM</itunes:keywords>
  <content:encoded>
    <![CDATA[<p>This week kicks off with a discussion of database indexes, Datalog, and Datomic. Amos wants to talk about error handling and when to report errors to an external service. He thinks that the goal should be to get the reported errors to zero, and Chris thinks that’s not possible. Chris explains the ways that he reports metrics and errors to collection services.</p>

<p>The conversation moves to circuit breakers and common patterns for handling overload in service calls.</p>

<p>Chris and Amos wrap up with some tips for debugging production problems with the scientific method.</p><p><a rel="payment" href="https://www.patreon.com/user?u=5332239">Support Elixir Outlaws</a></p><p>Links:</p><ul><li><a title="Datalog" rel="nofollow" href="https://en.wikipedia.org/wiki/Datalog">Datalog</a></li><li><a title="Datomic" rel="nofollow" href="https://www.datomic.com">Datomic</a></li><li><a title="Adaptive Queues for handling overload" rel="nofollow" href="https://www.youtube.com/watch?v=m64SWl9bfvk">Adaptive Queues for handling overload</a></li></ul>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>This week kicks off with a discussion of database indexes, Datalog, and Datomic. Amos wants to talk about error handling and when to report errors to an external service. He thinks that the goal should be to get the reported errors to zero, and Chris thinks that’s not possible. Chris explains the ways that he reports metrics and errors to collection services.</p>

<p>The conversation moves to circuit breakers and common patterns for handling overload in service calls.</p>

<p>Chris and Amos wrap up with some tips for debugging production problems with the scientific method.</p><p><a rel="payment" href="https://www.patreon.com/user?u=5332239">Support Elixir Outlaws</a></p><p>Links:</p><ul><li><a title="Datalog" rel="nofollow" href="https://en.wikipedia.org/wiki/Datalog">Datalog</a></li><li><a title="Datomic" rel="nofollow" href="https://www.datomic.com">Datomic</a></li><li><a title="Adaptive Queues for handling overload" rel="nofollow" href="https://www.youtube.com/watch?v=m64SWl9bfvk">Adaptive Queues for handling overload</a></li></ul>]]>
  </itunes:summary>
</item>
  </channel>
</rss>
