<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Domain Modeling on Nalar</title>
    <link>https://nalar.dev/tags/domain-modeling/</link>
    <description>Recent content in Domain Modeling 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/domain-modeling/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Replacing Primitive Data with Domain Types</title>
      <link>https://nalar.dev/replacing-primitive-data-with-domain-types/</link>
      <pubDate>Sat, 05 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/replacing-primitive-data-with-domain-types/</guid>
      <description>&lt;p&gt;Many bugs begin with a value that is technically valid for its programming-language type but invalid for the job it represents. A quantity is negative. A percentage is passed as &lt;code&gt;20&lt;/code&gt; where another function expects &lt;code&gt;0.20&lt;/code&gt;. Two string arguments are swapped because both look identical to the type system.&lt;/p&gt;&#xA;&lt;p&gt;The problem is not that strings and numbers are poor types. They are useful building blocks. The problem appears when a primitive value has accumulated rules or meaning that the primitive cannot express.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
