<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Disaster Recovery on No Semicolons</title><link>https://nosemicolons.com/tags/disaster-recovery/</link><description>Recent content in Disaster Recovery on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 19 Sep 2026 12:10:33 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/disaster-recovery/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Disaster Recovery Plan: How to Fix Everything When Your Model Generates 10,000 Lines of Broken Code</title><link>https://nosemicolons.com/posts/ai-code-generation-disaster-recovery-plan/</link><pubDate>Sat, 19 Sep 2026 12:10:33 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-disaster-recovery-plan/</guid><description>&lt;p>Picture this: You&amp;rsquo;re feeling confident about your AI-powered development workflow. You&amp;rsquo;ve been using Claude or GPT-4 to generate entire modules, and it&amp;rsquo;s been working beautifully. Then Monday morning hits, and you discover that Friday&amp;rsquo;s &amp;ldquo;quick AI generation session&amp;rdquo; produced 10,000 lines of subtly broken code that&amp;rsquo;s now tangled throughout your codebase like digital kudzu.&lt;/p>
&lt;p>I&amp;rsquo;ve been there. We&amp;rsquo;ve all been there. And if you haven&amp;rsquo;t yet, trust me—your time is coming.&lt;/p></description></item></channel></rss>