<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DevOps on Kuldeep Pisda</title><link>https://kdpisda.in/tag/devops/</link><description>Recent content in DevOps on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 03 Dec 2025 12:55:10 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>10 Continuous Integration Best Practices That Won't Make You Cry</title><link>https://kdpisda.in/10-continuous-integration-best-practices-that-wont-make-you-cry/</link><pubDate>Wed, 03 Dec 2025 12:55:10 +0530</pubDate><guid>https://kdpisda.in/10-continuous-integration-best-practices-that-wont-make-you-cry/</guid><description>&lt;p&gt;I once watched a startup&amp;rsquo;s entire deployment grind to a halt for a full day. The cause? A tiny, untested dependency change that snowballed into a cascade of failures. It was a classic &amp;lsquo;works on my machine&amp;rsquo; tragedy that cost them momentum and morale, a silent battle fought in the heart of their pipeline.&lt;/p&gt;
&lt;p&gt;That experience taught me a hard lesson: a Continuous Integration (CI) pipeline isn&amp;rsquo;t just an automation tool; it is the central nervous system of your engineering team. When it is healthy, you move fast and with confidence. When it is neglected, it becomes a source of constant friction, a tangled mess of slow builds, flaky tests, and deployment anxiety. This journey is about transforming that pipeline from a point of pain into a source of power.&lt;/p&gt;</description></item><item><title>Your Software Architecture Documentation Is Lying to You</title><link>https://kdpisda.in/your-software-architecture-documentation-is-lying-to-you/</link><pubDate>Thu, 27 Nov 2025 12:38:46 +0530</pubDate><guid>https://kdpisda.in/your-software-architecture-documentation-is-lying-to-you/</guid><description>&lt;p&gt;&amp;ldquo;The documentation is in the code.&amp;rdquo; I can&amp;rsquo;t count how many times I&amp;rsquo;ve heard this, usually from a well meaning senior engineer right before I spend the next three days spelunking through a codebase just to figure out what a single microservice is supposed to do.&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s be honest with each other. Most software architecture documentation is a ghost. It&amp;rsquo;s a pale, outdated echo of a system that once existed, haunting your Confluence space or a forgotten Google Drive folder. You follow the &lt;code&gt;README&lt;/code&gt;, and it breaks. You look at a diagram, and it shows services that were decommissioned a year ago.&lt;/p&gt;</description></item><item><title>10 Code Review Best Practices That Actually Work in 2025</title><link>https://kdpisda.in/10-code-review-best-practices-that-actually-work-in-2025/</link><pubDate>Sun, 23 Nov 2025 12:29:29 +0530</pubDate><guid>https://kdpisda.in/10-code-review-best-practices-that-actually-work-in-2025/</guid><description>&lt;p&gt;I once pushed a change that brought a production API to its knees. The culprit? A seemingly harmless database query that nobody caught in review. We have all been there: the endless back and forth, the vague &amp;lsquo;please fix&amp;rsquo; comments, the anxiety of hitting &amp;lsquo;merge&amp;rsquo;. Code review can feel like a chore, a bottleneck, or worse, a battleground. But what if it could be a team&amp;rsquo;s greatest superpower for learning and building resilient systems?&lt;/p&gt;</description></item><item><title>Django Website Hosting Made Simple</title><link>https://kdpisda.in/django-website-hosting-made-simple/</link><pubDate>Mon, 27 Oct 2025 15:16:47 +0530</pubDate><guid>https://kdpisda.in/django-website-hosting-made-simple/</guid><description>&lt;p&gt;Hosting a Django website means taking your application from your local computer and putting it on a server where the whole world can see it. This isn&amp;rsquo;t just about running &lt;code&gt;manage.py runserver&lt;/code&gt;. We&amp;rsquo;re talking about a real production setup with a &lt;strong&gt;WSGI server like Gunicorn&lt;/strong&gt;, a &lt;strong&gt;reverse proxy like Nginx&lt;/strong&gt;, and a robust &lt;strong&gt;database like PostgreSQL&lt;/strong&gt;.&lt;/p&gt;
&lt;h2 id="from-localhost-to-a-live-django-website"&gt;From Localhost To A Live Django Website&lt;a class="heading-anchor" href="#from-localhost-to-a-live-django-website" aria-hidden="true" tabindex="-1"&gt;#&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;Let&amp;rsquo;s be real: deploying your first Django app feels like a rite of passage. You&amp;rsquo;ve built something awesome on your machine, it runs perfectly, but getting it onto a live URL often feels like navigating a maze of acronyms and config files. It&amp;rsquo;s that leap every developer has to make—from the cozy, controlled world of &lt;code&gt;localhost&lt;/code&gt; to the wild west of the internet.&lt;/p&gt;</description></item></channel></rss>