<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code Cleanup on No Semicolons</title><link>https://nosemicolons.com/tags/code-cleanup/</link><description>Recent content in Code Cleanup on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 13 Sep 2026 12:59:23 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/code-cleanup/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Zombie Apocalypse: How Dead Code Is Silently Consuming Your Codebase</title><link>https://nosemicolons.com/posts/ai-code-generation-zombie-apocalypse-dead-code/</link><pubDate>Sun, 13 Sep 2026 12:59:23 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-zombie-apocalypse-dead-code/</guid><description>&lt;p>Ever noticed your codebase getting mysteriously heavier after a few months of AI-assisted coding? You&amp;rsquo;re not imagining it. While AI tools like GitHub Copilot and ChatGPT have revolutionized how we write code, they&amp;rsquo;ve also unleashed a subtle menace: an army of zombie functions, unused imports, and orphaned classes that shamble through our repositories, consuming resources and slowing us down.&lt;/p>
&lt;p>I learned this the hard way when my team&amp;rsquo;s main service started taking 40% longer to build, despite adding only modest new features. The culprit? Thousands of lines of AI-generated dead code that had accumulated like digital sediment over six months of enthusiastic AI-assisted development.&lt;/p></description></item></channel></rss>