<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Observability on No Semicolons</title><link>https://nosemicolons.com/tags/observability/</link><description>Recent content in Observability on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 20 Jul 2026 10:43:00 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/observability/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Monitoring Gap: How to Track Performance When You Don't Know What Your Model Actually Built</title><link>https://nosemicolons.com/posts/ai-code-generation-monitoring-gap/</link><pubDate>Mon, 20 Jul 2026 10:43:00 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-monitoring-gap/</guid><description>&lt;p>Picture this: your AI assistant just helped you build a complex data processing pipeline in 20 minutes that would have taken you hours to write from scratch. The code works beautifully in testing, you ship it to production, and then&amp;hellip; how do you monitor something you didn&amp;rsquo;t entirely build yourself?&lt;/p>
&lt;p>This is the AI code generation monitoring gap, and it&amp;rsquo;s becoming one of the most pressing challenges in AI-assisted development. When we let models generate significant portions of our code, we often end up with implementations that work but operate as partial black boxes. We understand the inputs and outputs, but the algorithmic choices, optimization strategies, and potential failure modes? Not so much.&lt;/p></description></item></channel></rss>