<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Object Design on Nalar</title>
    <link>https://nalar.dev/tags/object-design/</link>
    <description>Recent content in Object Design 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/object-design/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Put Decisions Next to the Data They Need</title>
      <link>https://nalar.dev/put-decisions-next-to-the-data-they-need/</link>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/put-decisions-next-to-the-data-they-need/</guid>
      <description>&lt;p&gt;A method can look perfectly reasonable while depending on far more knowledge than it should.&lt;/p&gt;&#xA;&lt;p&gt;Imagine checkout code that asks a customer object for &lt;code&gt;membershipLevel&lt;/code&gt;, &lt;code&gt;joinedAt&lt;/code&gt;, and &lt;code&gt;totalOrders&lt;/code&gt;, then combines those values to decide whether the customer receives priority support. The calculation works, but checkout now knows both the customer&amp;rsquo;s data and the rule that gives that data meaning.&lt;/p&gt;&#xA;&lt;p&gt;When the rule changes, every caller that reconstructed it becomes a possible edit site.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
