<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Developer Flow State on No Semicolons</title><link>https://nosemicolons.com/tags/developer-flow-state/</link><description>Recent content in Developer Flow State on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 11 Sep 2026 12:28:22 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/developer-flow-state/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Model Lag Crisis: How 200ms Response Times Are Destroying Developer Flow State</title><link>https://nosemicolons.com/posts/ai-code-generation-model-lag-crisis-response-times-flow-state/</link><pubDate>Fri, 11 Sep 2026 12:28:22 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-model-lag-crisis-response-times-flow-state/</guid><description>&lt;p>You know that feeling when you&amp;rsquo;re deep in the zone, fingers flying across the keyboard, and suddenly&amp;hellip; you wait. And wait. Your AI coding assistant is thinking, that little spinner is spinning, and by the time it responds, your train of thought has completely derailed.&lt;/p>
&lt;p>I&amp;rsquo;ve been there more times than I care to admit. That moment when a 500ms delay turns into a context switch that costs you 15 minutes of mental momentum. It turns out there&amp;rsquo;s actual science behind why these seemingly tiny delays are wreaking havoc on our productivity, and more importantly, there are practical ways to fix it.&lt;/p></description></item></channel></rss>