<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Code Quality - News</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Code Quality News feed</description>
    <item>
      <title>Discord Reveals How a Hidden Circular Dependency Triggered Its March Voice Outage</title>
      <link>https://www.infoq.com/news/2026/05/discord-circular-dependency/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Code+Quality-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/05/discord-circular-dependency/en/headerimage/generatedHeaderImage-1778423772865.jpg"/&gt;&lt;p&gt;Discord has released a detailed postmortem on its March 25, 2026, voice outage, revealing that a previously undetected circular dependency in its voice infrastructure triggered a cascading failure that disrupted voice services across the platform.&lt;/p&gt; &lt;i&gt;By Craig Risi&lt;/i&gt;</description>
      <category>Software Engineering</category>
      <category>Code Quality</category>
      <category>Failure</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Fri, 15 May 2026 12:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/05/discord-circular-dependency/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Code+Quality-news</guid>
      <dc:creator>Craig Risi</dc:creator>
      <dc:date>2026-05-15T12:00:00Z</dc:date>
      <dc:identifier>/news/2026/05/discord-circular-dependency/en</dc:identifier>
    </item>
    <item>
      <title>Anthropic Traces Six Weeks of Claude Code Quality Complaints to Three Overlapping Product Changes</title>
      <link>https://www.infoq.com/news/2026/05/anthropic-claude-code-postmortem/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Code+Quality-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/05/anthropic-claude-code-postmortem/en/headerimage/generatedHeaderImage-1778491231246.jpg"/&gt;&lt;p&gt;Anthropic published a postmortem tracing six weeks of Claude Code quality complaints to three overlapping product-layer changes: a reasoning effort downgrade, a caching bug that progressively erased the model's own thinking, and a system prompt verbosity limit that caused a 3% quality drop. The API and model weights were unaffected. All issues were resolved April 20.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Generative AI</category>
      <category>Anthropic</category>
      <category>AI Architecture</category>
      <category>Large language models</category>
      <category>Code Quality</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Thu, 14 May 2026 09:16:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/05/anthropic-claude-code-postmortem/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Code+Quality-news</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-05-14T09:16:00Z</dc:date>
      <dc:identifier>/news/2026/05/anthropic-claude-code-postmortem/en</dc:identifier>
    </item>
    <item>
      <title>Applying Best Simple System for Now for Software Design</title>
      <link>https://www.infoq.com/news/2026/05/best-simple-system-design/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Code+Quality-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/05/best-simple-system-design/en/headerimage/best-simple-system-design-header-1776687343321.jpg"/&gt;&lt;p&gt;Choosing between building up technical debt and missing delivery deadlines is a false dichotomy, Daniel Terhorst-North argued in his talk Best Simple System for Now. Programmers love to generalize rather than solve the immediate problem at hand, which can make future changes difficult. Instead, we need to build the skills and instincts for keeping things simple.&lt;/p&gt; &lt;i&gt;By Ben Linders&lt;/i&gt;</description>
      <category>Architecture</category>
      <category>Design</category>
      <category>GOTO Conference</category>
      <category>Scalability</category>
      <category>Technical Debt</category>
      <category>Code Quality</category>
      <category>Culture &amp; Methods</category>
      <category>news</category>
      <pubDate>Thu, 07 May 2026 11:43:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/05/best-simple-system-design/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Code+Quality-news</guid>
      <dc:creator>Ben Linders</dc:creator>
      <dc:date>2026-05-07T11:43:00Z</dc:date>
      <dc:identifier>/news/2026/05/best-simple-system-design/en</dc:identifier>
    </item>
  </channel>
</rss>
