<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code Validation on No Semicolons</title><link>https://nosemicolons.com/tags/code-validation/</link><description>Recent content in Code Validation on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 20 Apr 2026 09:51:56 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/code-validation/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Hallucination Detector: 5 Warning Signs Your Generated Code Is Fantasy</title><link>https://nosemicolons.com/posts/ai-code-hallucination-detector-warning-signs/</link><pubDate>Mon, 20 Apr 2026 09:51:56 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-hallucination-detector-warning-signs/</guid><description>&lt;p>Ever had that moment where you paste AI-generated code into your project, run it, and watch everything explode in spectacular fashion? You&amp;rsquo;re not alone. While AI coding assistants have become incredible partners in our development workflow, they sometimes generate code that looks absolutely perfect but is complete fantasy.&lt;/p>
&lt;p>I learned this the hard way when Claude confidently generated a Python function using a &amp;ldquo;vectorize_embeddings&amp;rdquo; method that simply doesn&amp;rsquo;t exist in any library I was using. It looked so legitimate that I spent 30 minutes troubleshooting my environment before realizing the AI had invented the entire API.&lt;/p></description></item></channel></rss>