<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI Code Smells on No Semicolons</title><link>https://nosemicolons.com/tags/ai-code-smells/</link><description>Recent content in AI Code Smells on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 04 Apr 2026 08:32:49 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/ai-code-smells/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Smell Detector: 8 Patterns That Signal Your Generated Code Will Fail</title><link>https://nosemicolons.com/posts/ai-code-smell-detector-patterns-generated-code-fails/</link><pubDate>Sat, 04 Apr 2026 08:32:49 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-smell-detector-patterns-generated-code-fails/</guid><description>&lt;p>You&amp;rsquo;re staring at a pull request filled with AI-generated code that passes all tests, looks syntactically correct, and even follows your team&amp;rsquo;s formatting guidelines. Everything seems perfect, but something feels&amp;hellip; off. Three weeks later, you&amp;rsquo;re debugging a production issue at 2 AM, tracing it back to that exact code.&lt;/p>
&lt;p>I&amp;rsquo;ve been there more times than I&amp;rsquo;d like to admit. After reviewing hundreds of AI-generated pull requests over the past year, I&amp;rsquo;ve noticed that AI assistants have their own unique &amp;ldquo;tells&amp;rdquo; — subtle patterns that often lead to problems down the road. These aren&amp;rsquo;t syntax errors or obvious bugs that your IDE will catch. They&amp;rsquo;re deeper architectural smells that can slip through code review and cause headaches in production.&lt;/p></description></item></channel></rss>