<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Python on Lorbic</title><link>http://localhost:1313/tags/python/</link><description>Recent content in Python on Lorbic</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 15 Feb 2026 13:45:00 +0530</lastBuildDate><atom:link href="http://localhost:1313/tags/python/index.xml" rel="self" type="application/rss+xml"/><item><title>Fast Docker CI: Stop Rebuilding Container Images on Every Commit</title><link>http://localhost:1313/stop-rebuilding-docker-images-runtime-containers/</link><pubDate>Sun, 15 Feb 2026 02:30:00 +0530</pubDate><guid>http://localhost:1313/stop-rebuilding-docker-images-runtime-containers/</guid><description>&lt;p>I used to rebuild my Docker image every time I fixed a typo. A one-line change meant waiting 2-3 minutes for Docker to rebuild layers, reinstall dependencies, and restart the container. I thought this was just the cost of containerized development.&lt;/p>
&lt;p>Then I discovered runtime containers. Same isolated environment, same reproducibility, but code changes reflect instantly. No rebuilds. No waiting. The runtime lives in the container, the code lives on the host.&lt;/p></description></item><item><title>Python Background Workers: Architecture, Queues, and Retry Strategies</title><link>http://localhost:1313/building-production-ready-background-workers-in-python/</link><pubDate>Sun, 01 Feb 2026 13:00:00 +0530</pubDate><guid>http://localhost:1313/building-production-ready-background-workers-in-python/</guid><description>&lt;p>I thought processing audio in the background was simple: spawn a thread, run the script, save the file. Then I hit 200 concurrent requests, and it failed epically.&lt;/p>
&lt;p>The CPU spiked to full usage because of pydub&amp;rsquo;s processing. The TTS API didn&amp;rsquo;t rate-limit me but, it was horribly slow. Then the jobs started failing. Half the jobs died silently. The other half wrote corrupted files because of race conditions I didn&amp;rsquo;t know existed. And when I deployed a little fix? The deployment killed in-flight jobs, leaving orphaned audio segments scattered across cloud storage directory.&lt;/p></description></item><item><title>I Added Session Management to Aider</title><link>http://localhost:1313/aider-session-management/</link><pubDate>Thu, 15 Jan 2026 20:30:00 +0530</pubDate><guid>http://localhost:1313/aider-session-management/</guid><description>&lt;p>I&amp;rsquo;ve been using &lt;a href="https://aider.chat" target="_blank" rel="noopener noreferrer">aider&lt;/a> as my primary AI coding assistant for a while now. It&amp;rsquo;s the one tool that actually fits my workflow: terminal-based, Git-native, and it works directly on my local files. No copy-pasting into web forms. No context windows that forget everything. And not waiting for agents to keep thinking.&lt;/p>
&lt;p>But it was missing one thing that drove me crazy.&lt;/p>
&lt;h2 id="the-problem-context-evaporates">The Problem: Context Evaporates&lt;a class="anchorjs-link" href="#the-problem-context-evaporates" aria-label="Link to section: The Problem: Context Evaporates">&lt;/a>&lt;/h2>&lt;p>Here&amp;rsquo;s the scenario. I&amp;rsquo;m deep into a complex refactor. I&amp;rsquo;ve added 15 files to the chat, built up tons of context with the model, and we&amp;rsquo;re making real progress.&lt;/p></description></item></channel></rss>