<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fake Frameworks on No Semicolons</title><link>https://nosemicolons.com/tags/fake-frameworks/</link><description>Recent content in Fake Frameworks on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 06 Jul 2026 11:57:14 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/fake-frameworks/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Hallucination Crisis: How to Spot When Your Model Is Making Up Frameworks That Don't Exist</title><link>https://nosemicolons.com/posts/ai-code-generation-hallucination-crisis-fake-frameworks/</link><pubDate>Mon, 06 Jul 2026 11:57:14 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-hallucination-crisis-fake-frameworks/</guid><description>&lt;p>Ever asked an AI to help you build something, only to spend hours debugging code that references a framework that&amp;hellip; doesn&amp;rsquo;t exist? Yeah, me too. Last week, I watched a colleague struggle with what seemed like a simple React component, until we realized the AI had confidently generated code using a completely fictional &amp;ldquo;react-smart-forms&amp;rdquo; library.&lt;/p>
&lt;p>This isn&amp;rsquo;t just an occasional hiccup—AI hallucination in code generation is becoming a real productivity killer. The more we rely on AI coding assistants, the more we need to get good at spotting when they&amp;rsquo;re making stuff up.&lt;/p></description></item></channel></rss>