<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai on Dvir Segal's blog</title><link>https://dvirsegal.github.io/tags/ai/</link><description>Recent content in Ai on Dvir Segal's blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 02 Oct 2026 20:32:36 +0000</lastBuildDate><atom:link href="https://dvirsegal.github.io/tags/ai/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Approved the PR. Nobody Knows Why the Code Works.</title><link>https://dvirsegal.github.io/posts/ai-approved-the-pr-nobody-knows-why-the-code-works-a7f71e96dd63/</link><pubDate>Fri, 02 Oct 2026 20:32:36 +0000</pubDate><guid>https://dvirsegal.github.io/posts/ai-approved-the-pr-nobody-knows-why-the-code-works-a7f71e96dd63/</guid><description>&lt;p&gt;Picture this, you open a PR and the AI report is already waiting. Three findings, all minor. You skim the diff, approve, and move on. A month later someone asks why that service retries three times instead of failing fast. The author doesn’t know, because an agent wrote it. You don’t know either, and you approved it.&lt;/p&gt;&#10;&#10;&#10;&#10;&#10;&lt;div style="text-align: center;"&gt;&#10; &lt;img src="https://dvirsegal.github.io/images/ai-approved-the-pr-nobody-knows-why-the-code-works-a7f71e96dd63/2.png" alt="LEGO-style scene, one month later: a developer asks why the service retries three times instead of failing fast, while the author shrugs and the reviewer holds an APPROVED stamp" style="display: block; margin: 0 auto;" /&gt;&#10; &#10;&lt;/div&gt;&#10;&#10;&lt;p&gt;I review PRs with an &lt;a href="https://gist.github.com/dvirsegal/987e1d5dbd423640e86d9102e80edf1c" class="external-link" target="_blank" rel="noopener"&gt;AI code review workflow&lt;/a&gt; (gist) that maps the blast radius of each change with &lt;a href="https://colbymchenry.github.io/codegraph/" class="external-link" target="_blank" rel="noopener"&gt;CodeGraph&lt;/a&gt;, a local tool that turns the codebase into a queryable graph of callers and callees, and reports findings by severity. It catches real bugs. It can’t tell me why the code is the way it is.&lt;/p&gt;</description></item></channel></rss>