<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cost-Optimization on No Semicolons</title><link>https://nosemicolons.com/tags/cost-optimization/</link><description>Recent content in Cost-Optimization on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 26 Jun 2026 10:44:38 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/cost-optimization/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Cache Miss: How I Reduced Development Costs by 60% with Smart Context Reuse</title><link>https://nosemicolons.com/posts/ai-code-generation-cache-miss-reduce-costs-context-reuse/</link><pubDate>Fri, 26 Jun 2026 10:44:38 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-cache-miss-reduce-costs-context-reuse/</guid><description>&lt;p>Ever noticed how your AI coding bills keep climbing while you&amp;rsquo;re essentially asking the same questions over and over? I was burning through my Claude and GPT-4 credits faster than I could justify, until I realized I was treating every conversation like a blank slate.&lt;/p>
&lt;p>Last month, I decided to track exactly where my tokens were going. The results were eye-opening: I was spending 60% of my AI budget on redundant context that I&amp;rsquo;d already established in previous conversations. We&amp;rsquo;re talking about explaining the same codebase architecture, repeating coding standards, and re-establishing project context dozens of times per week.&lt;/p></description></item></channel></rss>