<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>code quality on Kuldeep Pisda</title><link>https://kdpisda.in/tag/code-quality/</link><description>Recent content in code quality on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 26 Nov 2025 12:57:56 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/code-quality/index.xml" rel="self" type="application/rss+xml"/><item><title>What Is Test Driven Development? A Guide to Saner Coding</title><link>https://kdpisda.in/what-is-test-driven-development-a-guide-to-saner-coding/</link><pubDate>Thu, 02 Oct 2025 12:14:42 +0530</pubDate><guid>https://kdpisda.in/what-is-test-driven-development-a-guide-to-saner-coding/</guid><description>&lt;p&gt;We’ve all been there. It’s &lt;strong&gt;10 PM&lt;/strong&gt; on a Tuesday, and an alert screams from your monitoring dashboard. A critical feature, one that was working perfectly just hours ago, has suddenly broken in production.&lt;/p&gt;
&lt;p&gt;The pressure mounts with every passing minute as you dive into the codebase, frantically trying to pinpoint the source of the chaos. Every change you consider feels like a massive gamble. Did your last deployment cause this? Was it an obscure edge case nobody thought of? Fixing one thing might silently break three others. I once spent an entire afternoon chasing a bug like this, only to find a single misplaced comma. It&amp;rsquo;s maddening.&lt;/p&gt;</description></item></channel></rss>