<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Code Review on Nalar</title>
    <link>https://nalar.dev/tags/code-review/</link>
    <description>Recent content in Code Review on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 02 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/code-review/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Code Reviews That Improve Change Quality</title>
      <link>https://nalar.dev/code-reviews-that-improve-change-quality/</link>
      <pubDate>Wed, 02 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/code-reviews-that-improve-change-quality/</guid>
      <description>&lt;p&gt;Code review is one of the few engineering practices that can improve a change before it reaches production while also spreading knowledge across a team. It can catch defects, expose unclear assumptions, improve maintainability, and help engineers understand parts of the system they did not write.&lt;/p&gt;&#xA;&lt;p&gt;It can also become slow and frustrating when reviewers focus on preferences, authors submit changes that are too large to reason about, or nobody is clear about what approval means.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
