<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Migration Safety on No Semicolons</title><link>https://nosemicolons.com/tags/migration-safety/</link><description>Recent content in Migration Safety on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 13 Aug 2026 09:04:08 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/migration-safety/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Database Migration Disaster: How I Lost 3TB of Production Data (And the 5-Step Recovery Protocol That Saved Everything)</title><link>https://nosemicolons.com/posts/ai-code-generation-database-migration-disaster-recovery-protocol/</link><pubDate>Thu, 13 Aug 2026 09:04:08 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-database-migration-disaster-recovery-protocol/</guid><description>&lt;p>Picture this: It&amp;rsquo;s 2 AM, you&amp;rsquo;re sipping your third coffee, and you just watched an AI-generated migration script delete three terabytes of production data in under thirty seconds. That was my Tuesday last month, and honestly, it&amp;rsquo;s a mistake I hope you never have to make.&lt;/p>
&lt;p>But here&amp;rsquo;s the thing – I recovered everything. And more importantly, I learned a bulletproof system for working with AI on database operations that I&amp;rsquo;m going to share with you today.&lt;/p></description></item></channel></rss>