<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI Model Temperature on No Semicolons</title><link>https://nosemicolons.com/tags/ai-model-temperature/</link><description>Recent content in AI Model Temperature on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 25 Jul 2026 09:29:40 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/ai-model-temperature/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Model Temperature Crisis: How 0.7 vs 0.1 Settings Are Making or Breaking Your Production Code</title><link>https://nosemicolons.com/posts/ai-code-generation-temperature-settings-production/</link><pubDate>Sat, 25 Jul 2026 09:29:40 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-temperature-settings-production/</guid><description>&lt;p>Ever shipped code that worked perfectly in your AI assistant but broke spectacularly in production? You might be fighting the wrong battle. While we obsess over which AI model to use, there&amp;rsquo;s a hidden culprit sabotaging our code quality: temperature settings.&lt;/p>
&lt;p>I spent the last month running the same coding tasks through different AI model configurations, and the results were eye-opening. The difference between a temperature of 0.1 and 0.7 isn&amp;rsquo;t just academic—it&amp;rsquo;s the difference between bulletproof production code and a debugging nightmare.&lt;/p></description></item></channel></rss>