<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI Resilience on No Semicolons</title><link>https://nosemicolons.com/tags/ai-resilience/</link><description>Recent content in AI Resilience on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 05 Jul 2026 10:04:16 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/ai-resilience/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation API Rate Limit Crisis: How to Build Production Apps When Your Models Go Down</title><link>https://nosemicolons.com/posts/ai-code-generation-api-rate-limits-production-apps/</link><pubDate>Sun, 05 Jul 2026 10:04:16 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-api-rate-limits-production-apps/</guid><description>&lt;p>Picture this: it&amp;rsquo;s 2 AM, your AI-powered app is processing a critical batch job, and suddenly Claude stops responding. Your users are staring at loading spinners, your error logs are exploding, and you&amp;rsquo;re frantically refreshing the Anthropic status page. Sound familiar?&lt;/p>
&lt;p>We&amp;rsquo;ve all been there. The dirty secret of modern AI development is that we&amp;rsquo;re building on quicksand. These model APIs that feel so reliable during development have a nasty habit of disappearing exactly when you need them most.&lt;/p></description></item></channel></rss>