<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code Review on Coderrob</title><link>https://coderrob.com/tags/code-review/</link><description>Recent content in Code Review on Coderrob</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 21 Jul 2026 09:00:00 -0500</lastBuildDate><atom:link href="https://coderrob.com/tags/code-review/index.xml" rel="self" type="application/rss+xml"/><item><title>Functional Documentation Is an Agentic Guardrail</title><link>https://coderrob.com/posts/functional-documentation-is-an-agentic-guardrail/</link><pubDate>Tue, 21 Jul 2026 09:00:00 -0500</pubDate><guid>https://coderrob.com/posts/functional-documentation-is-an-agentic-guardrail/</guid><description>&lt;p&gt;&lt;strong&gt;Functional documentation becomes more valuable, not less, when AI agents are writing and reviewing code.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;I heard an architect argue that, in the age of AI agents, functional documentation in source code was no longer necessary. The agent can read the code, after all. Why explain what a function does when the implementation is sitting right there?&lt;/p&gt;
&lt;p&gt;My first reaction was that the opinion was somewhat absurd and potentially dangerous.&lt;/p&gt;</description></item><item><title>Agentic Development and the Review-Centric Workflow</title><link>https://coderrob.com/posts/agentic-development-review-centric-workflow/</link><pubDate>Thu, 14 May 2026 00:00:00 -0500</pubDate><guid>https://coderrob.com/posts/agentic-development-review-centric-workflow/</guid><description>&lt;p&gt;AI is going to change software teams whether we pretend to be ready or not.&lt;/p&gt;
&lt;p&gt;The lazy version of that change is simple: give everyone an agent, tell them to go faster, and hope review catches whatever falls out the other side.&lt;/p&gt;
&lt;p&gt;That is not a strategy.&lt;/p&gt;
&lt;p&gt;The better version is this:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Move humans closer to design and review, then let agents help execute well-defined units of work.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;That does not mean developers stop being technical. It means the team&amp;rsquo;s technical energy shifts toward architecture, decomposition, design patterns, refactoring, review, verification, and shared understanding.&lt;/p&gt;</description></item><item><title>Trust but Verify: The Math of Rigorous Software Development</title><link>https://coderrob.com/posts/trust-but-verify-the-math-of-rigorous-software-development/</link><pubDate>Fri, 10 Apr 2026 10:00:00 -0500</pubDate><guid>https://coderrob.com/posts/trust-but-verify-the-math-of-rigorous-software-development/</guid><description>&lt;h2 id="between-satire-and-ridicule"&gt;Between Satire and Ridicule&lt;/h2&gt;
&lt;p&gt;It started, as these things often do, with a comparison nobody asked for.&lt;/p&gt;
&lt;p&gt;I made a post saying that, with AI-assisted workflows, I can contribute anywhere from &lt;strong&gt;20 to 300,000 lines of change in a day&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;That number was not meant to say, &amp;ldquo;Look at me, I make ALL the tokens go brrrrrrrt&amp;hellip;&amp;rdquo;&lt;/p&gt;
&lt;p&gt;It was me counting additions plus deletions across real work: feature creation, refactoring, documentation, automation, test updates, generated assets, project scaffolding, cleanup, and the supporting files needed to make the work sustainable.&lt;/p&gt;</description></item></channel></rss>