<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI Migration on No Semicolons</title><link>https://nosemicolons.com/tags/ai-migration/</link><description>Recent content in AI Migration on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 03 Sep 2026 12:23:48 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/ai-migration/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Rollforward Crisis: How to Safely Upgrade When Your Model Stops Supporting Your Favorite Prompts</title><link>https://nosemicolons.com/posts/ai-code-generation-rollforward-crisis-model-upgrade-strategy/</link><pubDate>Thu, 03 Sep 2026 12:23:48 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-rollforward-crisis-model-upgrade-strategy/</guid><description>&lt;p>You wake up Monday morning, grab your coffee, and fire up your development environment. Your carefully crafted prompt that&amp;rsquo;s been generating perfect boilerplate code for months suddenly returns gibberish. Sound familiar?&lt;/p>
&lt;p>Welcome to the AI code generation rollforward crisis — that gut-punch moment when your trusted AI model gets updated and your finely-tuned prompts stop working. It happened to me last month with a critical prompt I&amp;rsquo;d been using for React component generation, and I learned some hard lessons about model dependency the expensive way.&lt;/p></description></item></channel></rss>