<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Best Practices on Nalar</title>
    <link>https://nalar.dev/tags/best-practices/</link>
    <description>Recent content in Best Practices on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 01 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/best-practices/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go Error Wrapping with errors.Is and errors.As</title>
      <link>https://nalar.dev/go-error-wrapping-errors-is-errors-as/</link>
      <pubDate>Tue, 01 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/go-error-wrapping-errors-is-errors-as/</guid>
      <description>&lt;p&gt;Errors often cross several layers of a Go application. A low-level function may know that a file is missing, while a higher-level function needs to add context about which operation failed. Go error wrapping lets you add that context without losing information callers need for reliable handling.&lt;/p&gt;&#xA;&lt;h2 id=&#34;why-error-strings-are-fragile&#34;&gt;Why error strings are fragile&lt;/h2&gt;&#xA;&lt;p&gt;Do not make program logic depend on error wording. Adding a filename or changing punctuation can break string comparisons even when the underlying condition is unchanged. Prefer semantic checks:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
