<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Technical-Debt on Kuldeep Pisda</title><link>https://kdpisda.in/tag/technical-debt/</link><description>Recent content in Technical-Debt on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 28 Jan 2026 10:00:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/technical-debt/index.xml" rel="self" type="application/rss+xml"/><item><title>The 1.2 GB Video We Chose Not to Fix</title><link>https://kdpisda.in/the-video-we-chose-not-to-fix/</link><pubDate>Wed, 28 Jan 2026 10:00:00 +0530</pubDate><guid>https://kdpisda.in/the-video-we-chose-not-to-fix/</guid><description>&lt;p&gt;The FastAPI proxy had done exactly what I built it to do. It kept the course screen fast, bolted CCAvenue payments onto the edge, and carried us from 2,000 users to roughly 6,000 in three months with about one in ten paying. But the proxy fixed the wrong end of the pipe. It made the &lt;em&gt;metadata&lt;/em&gt; fast. It did nothing for the thing users actually came for: the video. And the video had a problem I could not cache my way out of.&lt;/p&gt;</description></item></channel></rss>