<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MLOps on No Semicolons</title><link>https://nosemicolons.com/tags/mlops/</link><description>Recent content in MLOps on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 04 Jul 2026 10:01:27 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/mlops/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Data Science Disconnect: Why Your ML Model Training Code Never Works in Production</title><link>https://nosemicolons.com/posts/ai-code-generation-data-science-disconnect/</link><pubDate>Sat, 04 Jul 2026 10:01:27 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-data-science-disconnect/</guid><description>&lt;p>Ever asked Claude or ChatGPT to help you deploy a machine learning model, only to watch it confidently generate code that immediately crashes with a cryptic CUDA error? You&amp;rsquo;re not alone, and it&amp;rsquo;s not your fault.&lt;/p>
&lt;p>I&amp;rsquo;ve been building ML systems for the past few years, and I&amp;rsquo;ve noticed something fascinating: AI code generation tools that work beautifully for web development seem to hit a wall when it comes to data science. That elegant React component? Generated flawlessly. That FastAPI endpoint? Perfect on the first try. But ask for help moving your PyTorch model from Jupyter notebook to production, and suddenly you&amp;rsquo;re debugging dependency conflicts at 2 AM.&lt;/p></description></item></channel></rss>