<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Coupling on Nalar</title>
    <link>https://nalar.dev/tags/coupling/</link>
    <description>Recent content in Coupling on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 05 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/coupling/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Reducing Object Graph Coupling with the Law of Demeter</title>
      <link>https://nalar.dev/reducing-object-graph-coupling-with-the-law-of-demeter/</link>
      <pubDate>Sat, 05 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/reducing-object-graph-coupling-with-the-law-of-demeter/</guid>
      <description>&lt;p&gt;A small change to an object model can cause surprising edits far away from the changed class. A developer moves an address under a customer profile, for example, and code in pricing, notifications, and reporting all breaks because each caller navigates the same chain of objects.&lt;/p&gt;&#xA;&lt;p&gt;The immediate problem looks like missing properties. The deeper problem is that those callers know the &lt;em&gt;shape&lt;/em&gt; of an object graph they do not own.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
