<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Automation</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Automation feed</description>
    <item>
      <title>DoorDash Uses Multi Agent LLMs to Clean up 60,000 Feature Flags</title>
      <link>https://www.infoq.com/news/2026/09/doordash-feature-flag-cleanup/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Automation</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/09/doordash-feature-flag-cleanup/en/headerimage/generatedHeaderImage-1788418529526.jpg"/&gt;&lt;p&gt;DoorDash built a multi-agent LLM system to automate stale feature flag cleanup across more than 60,000 flags and 623 repositories. The workflow combines live experimentation data through MCP, engineer approval, isolated Git worktrees, parallel agents, and automated validation. In an evaluation of 50 flags, 45 produced usable pull requests at an average of 13.8 minutes and $4.79 per cleanup.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Static Analysis</category>
      <category>Developer Experience</category>
      <category>A/B Testing</category>
      <category>Agents</category>
      <category>Feature Injection</category>
      <category>Experiment Driven Development</category>
      <category>github</category>
      <category>Feature Toggle</category>
      <category>Large language models</category>
      <category>git</category>
      <category>AI Coding</category>
      <category>AI Assisted Coding</category>
      <category>Productivity</category>
      <category>Automation</category>
      <category>AI Architecture</category>
      <category>Model Context Protocol (MCP)</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Fri, 18 Sep 2026 13:50:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/09/doordash-feature-flag-cleanup/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Automation</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-09-18T13:50:00Z</dc:date>
      <dc:identifier>/news/2026/09/doordash-feature-flag-cleanup/en</dc:identifier>
    </item>
    <item>
      <title>Presentation: Teaching Engineers, Trusting AI: How Education Enabled Autonomous Code Review</title>
      <link>https://www.infoq.com/presentations/duolingo-ai-literacy-code-review/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Automation</link>
      <description>&lt;img src="https://res.infoq.com/presentations/duolingo-ai-literacy-code-review/en/mediumimage/sarah-deitke-medium-1788338781338.jpeg"/&gt;&lt;p&gt;Sarah Deitke discusses how Duolingo drives cultural AI adoption beyond tooling access. She explains their internal AI literacy workshops and observability dashboards, then shares a case study on redesigning code review using an automated PR risk-assessment bot. Deitke demonstrates how pairing targeted developer education with safe AI guardrails speeds up delivery without increasing defect rates.&lt;/p&gt; &lt;i&gt;By Sarah Deitke&lt;/i&gt;</description>
      <category>Developer Experience</category>
      <category>Culture</category>
      <category>QCon London 2026</category>
      <category>Adoption</category>
      <category>Transcripts</category>
      <category>Artificial Intelligence</category>
      <category>Metrics</category>
      <category>Automation</category>
      <category>Code Reviews</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Culture &amp; Methods</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>presentation</category>
      <pubDate>Wed, 16 Sep 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/presentations/duolingo-ai-literacy-code-review/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Automation</guid>
      <dc:creator>Sarah Deitke</dc:creator>
      <dc:date>2026-09-16T11:00:00Z</dc:date>
      <dc:identifier>/presentations/duolingo-ai-literacy-code-review/en</dc:identifier>
    </item>
    <item>
      <title>Article: Implementing Durable Workflows on Postgres Without an External Orchestrator</title>
      <link>https://www.infoq.com/articles/durable-workflows-postgres/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Automation</link>
      <description>&lt;img src="https://res.infoq.com/articles/durable-workflows-postgres/en/headerimage/Implementing-Durable-Workflows-on-Postgres-Without-an-External-Orchestrator-header-1789129413946.jpg"/&gt;&lt;p&gt;Postgres can serve as the durable state store and coordination layer for workflows, eliminating the need for an external orchestrator. SKIP LOCKED enables concurrent work processing, primary-key checkpoints enforce idempotency, and leases support crash recovery. Workflow sleeps and human approvals can also be persisted as database state and survive restarts.&lt;/p&gt; &lt;i&gt;By Raman Varma&lt;/i&gt;</description>
      <category>Relational Databases</category>
      <category>Orchestration</category>
      <category>Postgres</category>
      <category>Queue</category>
      <category>Automation</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Mon, 14 Sep 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/durable-workflows-postgres/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Automation</guid>
      <dc:creator>Raman Varma</dc:creator>
      <dc:date>2026-09-14T11:00:00Z</dc:date>
      <dc:identifier>/articles/durable-workflows-postgres/en</dc:identifier>
    </item>
  </channel>
</rss>
