<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Code-Quality on guy@secdev.uk</title>
    <link>https://www.secdev.uk/blog/tags/code-quality/</link>
    <description>Recent content in Code-Quality on guy@secdev.uk</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <copyright>Guy Dixon | guy@secdev.uk</copyright>
    <lastBuildDate>Mon, 27 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.secdev.uk/blog/tags/code-quality/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AI and the Changing Nature of Code Review</title>
      <link>https://www.secdev.uk/blog/leadership/4.7-ai-and-the-changing-nature-of-code-review/</link>
      <pubDate>Mon, 27 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/4.7-ai-and-the-changing-nature-of-code-review/</guid>
      <description>&lt;p&gt;Code review has always been one of the most valuable practices in software engineering, not just for catching bugs, but for sharing knowledge, maintaining standards, and building collective ownership of the codebase. With AI-generated code becoming a significant portion of what gets reviewed, the practice needs to evolve.&lt;/p&gt;&#xA;&lt;p&gt;The fundamental shift is this: when a human writes code, the reviewer can assume the author understood what they wrote and made deliberate choices. When AI generates code, that assumption doesn&#39;t hold. The reviewer&#39;s job changes from &amp;quot;verify that a competent colleague made reasonable choices&amp;quot; to &amp;quot;verify that a probabilistic text generator produced correct, secure, maintainable code.&amp;quot; That&#39;s a harder job, and it requires different skills.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Technical Debt Nobody&#39;s Talking About: AI-Generated Code at Scale</title>
      <link>https://www.secdev.uk/blog/leadership/4.5-ai-technical-debt/</link>
      <pubDate>Mon, 13 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/4.5-ai-technical-debt/</guid>
      <description>&lt;p&gt;Technical debt is a concept every engineering leader understands. We make deliberate trade-offs, shipping something imperfect now to deliver value sooner, with the intention of paying down the debt later. AI-generated code introduces a new category of debt that&#39;s less deliberate and harder to see.&lt;/p&gt;&#xA;&lt;p&gt;The more I&#39;ve watched teams adopt AI coding assistants, the more concerned I&#39;ve become about what&#39;s accumulating beneath the surface. Not because AI-generated code is bad, it&#39;s often perfectly functional. But &amp;quot;functional&amp;quot; and &amp;quot;maintainable&amp;quot; are different things, and the gap between them is where this new debt lives.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
