<?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>Errors on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/errors/</link>
    <description>Recent content in Errors on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 11 Sep 2019 11:58:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/errors/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Error Handling in Go: Patterns That Actually Work at Scale</title>
      <link>https://blog.turboawesome.win/2019/09/error-handling-in-go-patterns-that-actually-work-at-scale/</link>
      <pubDate>Wed, 11 Sep 2019 11:58:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2019/09/error-handling-in-go-patterns-that-actually-work-at-scale/</guid>
      <description>Go&amp;#39;s error handling is explicit and verbose by design. At scale — hundreds of functions, multiple layers, concurrent operations — the naive patterns break down. These are the patterns that held up.</description>
    </item>
  </channel>
</rss>
