<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Units-of-Measure on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/units-of-measure/</link>
    <description>Recent content in Units-of-Measure on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 17 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/units-of-measure/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>UnitsNet vs QuantityTypes vs UnitGenerator: Picking a .NET Units of Measure Library in 2026</title>
      <link>https://www.pistack.xyz/posts/2026-09-17-dotnet-units-of-measure-libraries-unitsnet-quantitytypes-unitgenerator/</link>
      <pubDate>Thu, 17 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-17-dotnet-units-of-measure-libraries-unitsnet-quantitytypes-unitgenerator/</guid>
      <description>&lt;p&gt;There is a specific class of production bug that no unit test catches, because the test asserts the wrong thing with total confidence. A spacecraft&amp;rsquo;s ground software loses a probe because pound-force and newton were conflated. A billing pipeline issues refunds in cents where the ledger expected dollars. An engineering dashboard reports a beam&amp;rsquo;s deflection in millimetres and a reviewer signs off because the number looks plausible. Every one of those bugs is a &lt;em&gt;type&lt;/em&gt; bug: the program had a &lt;code&gt;double&lt;/code&gt; where it needed a &lt;code&gt;Length&lt;/code&gt;, and &lt;code&gt;double&lt;/code&gt; never objects.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
