<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Modularity on Nalar</title>
    <link>https://nalar.dev/tags/modularity/</link>
    <description>Recent content in Modularity on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 03 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/modularity/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Designing Modules Around Cohesion and Coupling</title>
      <link>https://nalar.dev/designing-modules-around-cohesion-and-coupling/</link>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/designing-modules-around-cohesion-and-coupling/</guid>
      <description>&lt;p&gt;A codebase can be split into many files and still be difficult to change. A small feature may require edits in several modules, tests may need large fixtures, and one internal change may unexpectedly break distant code.&lt;/p&gt;&#xA;&lt;p&gt;The problem is often not the number of modules. It is where their boundaries are drawn.&lt;/p&gt;&#xA;&lt;p&gt;Two ideas are especially useful when evaluating those boundaries: &lt;strong&gt;cohesion&lt;/strong&gt; and &lt;strong&gt;coupling&lt;/strong&gt;. Cohesion asks whether the responsibilities inside a module belong together. Coupling asks how much one module depends on the details of another. Used together, they provide a practical way to decide where code should live and which dependencies deserve attention.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
