<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code Readability on No Semicolons</title><link>https://nosemicolons.com/tags/code-readability/</link><description>Recent content in Code Readability on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 16 Apr 2026 09:11:00 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/code-readability/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Comment Anti-Pattern: Why Generated Comments Are Making Your Codebase Worse</title><link>https://nosemicolons.com/posts/ai-code-comment-anti-pattern-making-codebase-worse/</link><pubDate>Thu, 16 Apr 2026 09:11:00 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-comment-anti-pattern-making-codebase-worse/</guid><description>&lt;p>Have you ever opened a file and found comments like &lt;code>// This function calculates the total&lt;/code> right above a function called &lt;code>calculateTotal()&lt;/code>? If you&amp;rsquo;re using AI coding assistants regularly, you&amp;rsquo;ve probably seen this more than you&amp;rsquo;d like to admit.&lt;/p>
&lt;p>I&amp;rsquo;ve been wrestling with this problem in my own projects lately. AI tools are incredible at generating code, but their default approach to comments often creates more noise than signal. After spending way too much time cleaning up AI-generated documentation, I&amp;rsquo;ve learned some hard lessons about when to keep, modify, or completely skip the comments our AI companions want to add.&lt;/p></description></item></channel></rss>