<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>pull request on Kuldeep Pisda</title><link>https://kdpisda.in/tag/pull-request/</link><description>Recent content in pull request on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 23 Nov 2025 12:29:28 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/pull-request/index.xml" rel="self" type="application/rss+xml"/><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></channel></rss>