<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Resilience</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Resilience feed</description>
    <item>
      <title>Presentation: How to Find Resilience Bugs in Systems that Don't Exist</title>
      <link>https://www.infoq.com/presentations/formal-methods-principles/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Resilience</link>
      <description>&lt;img src="https://res.infoq.com/presentations/formal-methods-principles/en/mediumimage/hillel-wayne-medium-1790846078119.jpeg"/&gt;&lt;p&gt;Hillel Wayne discusses how formal methods principles - such as property strength, state-space verification, and environment assumptions - help software engineers uncover critical architectural bugs early. He shares practical mental models like "adversarial non-determinism" to reason about concurrency, edge cases, and distributed system failures without needing complex mathematical tools.&lt;/p&gt; &lt;i&gt;By Hillel Wayne&lt;/i&gt;</description>
      <category>Debugging</category>
      <category>Concurrency</category>
      <category>Resilience</category>
      <category>Reliability</category>
      <category>QCon London 2026</category>
      <category>Transcripts</category>
      <category>Verification</category>
      <category>Distributed Systems</category>
      <category>Architecture &amp; Design</category>
      <category>Culture &amp; Methods</category>
      <category>Development</category>
      <category>presentation</category>
      <pubDate>Wed, 14 Oct 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/presentations/formal-methods-principles/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Resilience</guid>
      <dc:creator>Hillel Wayne</dc:creator>
      <dc:date>2026-10-14T11:00:00Z</dc:date>
      <dc:identifier>/presentations/formal-methods-principles/en</dc:identifier>
    </item>
  </channel>
</rss>
