<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Performance Tuning on No Semicolons</title><link>https://nosemicolons.com/tags/performance-tuning/</link><description>Recent content in Performance Tuning on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 17 Sep 2026 12:54:32 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/performance-tuning/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Localhost Bottleneck: Why Your Dev Environment Is the Real Performance Problem</title><link>https://nosemicolons.com/posts/ai-code-generation-localhost-bottleneck-dev-environment-performance/</link><pubDate>Thu, 17 Sep 2026 12:54:32 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-localhost-bottleneck-dev-environment-performance/</guid><description>&lt;p>Ever noticed how that brilliant AI-generated React component takes forever to hot reload, or how your freshly minted API endpoint seems to crawl when you test it locally? You&amp;rsquo;re probably blaming the AI for generating &amp;ldquo;slow&amp;rdquo; code, but I&amp;rsquo;ve got news for you: the bottleneck isn&amp;rsquo;t in the generated code—it&amp;rsquo;s sitting right there in your localhost setup.&lt;/p>
&lt;p>After months of optimizing my AI development workflow, I&amp;rsquo;ve discovered that most performance complaints about AI-generated code actually stem from poorly configured local environments. We&amp;rsquo;re so focused on prompt engineering and model selection that we&amp;rsquo;re ignoring the foundation everything runs on.&lt;/p></description></item></channel></rss>