<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - StoryTeller - Podcasts</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ StoryTeller Podcasts feed</description>
    <item>
      <title>Podcast: Failure As a Means to Build Resilient Software Systems: A Conversation with Lorin Hochstein</title>
      <link>https://www.infoq.com/podcasts/failure-means-build-resilient-software-system/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=StoryTeller-podcasts</link>
      <description>&lt;img src="https://res.infoq.com/podcasts/failure-means-build-resilient-software-system/en/smallimage/the-infoq-podcast-logo-thumbnail-1774429354741.jpg"/&gt;&lt;p&gt;In this podcast Michael Stiefel spoke to Lorin Hochstein about how real-world failures provide insight into how software systems actually work. Our first topic was understanding that while automated fault injection tools can introduce basic robustness into a system, they cannot replicate the understanding that comes from mitigating complicated software failures in the real world.&lt;/p&gt; &lt;i&gt;By Lorin Hochstein&lt;/i&gt;</description>
      <category>Failure</category>
      <category>The InfoQ Podcast</category>
      <category>Software Engineering</category>
      <category>learning</category>
      <category>StoryTeller</category>
      <category>Architecture</category>
      <category>Design</category>
      <category>Architecture &amp; Design</category>
      <category>podcast</category>
      <pubDate>Tue, 31 Mar 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/podcasts/failure-means-build-resilient-software-system/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=StoryTeller-podcasts</guid>
      <dc:creator>Lorin Hochstein</dc:creator>
      <dc:date>2026-03-31T09:00:00Z</dc:date>
      <dc:identifier>/podcasts/failure-means-build-resilient-software-system/en</dc:identifier>
    </item>
  </channel>
</rss>
