<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Error-Handling on The Struggling Historian</title>
    <link>https://strugglinghistorian.me/tags/error-handling/</link>
    <description>Recent content in Error-Handling on The Struggling Historian</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 15 Jun 2026 10:00:00 +0200</lastBuildDate>
    <atom:link href="https://strugglinghistorian.me/tags/error-handling/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Error Tracing: Lessons Learned From the Trenches</title>
      <link>https://strugglinghistorian.me/talks/error-tracing-lessons-from-the-trenches/</link>
      <pubDate>Mon, 15 Jun 2026 10:00:00 +0200</pubDate>
      <guid>https://strugglinghistorian.me/talks/error-tracing-lessons-from-the-trenches/</guid>
      <description>Three real anti-patterns from production Go code that show how errors lose meaning, context, and safety as they travel through a layered architecture — and the single architectural principle that fixes all three.</description>
    </item>
  </channel>
</rss>
