<?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>Zap on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/zap/</link>
    <description>Recent content in Zap on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 07 Oct 2025 09:15:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/zap/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Migrating a Production Service from Zap to slog: Notes from the Trenches</title>
      <link>https://blog.turboawesome.win/2025/10/migrating-a-production-service-from-zap-to-slog-notes-from-the-trenches/</link>
      <pubDate>Tue, 07 Oct 2025 09:15:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2025/10/migrating-a-production-service-from-zap-to-slog-notes-from-the-trenches/</guid>
      <description>log/slog landed in the standard library in Go 1.21, but most production services are still on zap or zerolog. Here is what an actual migration looks like: where slog wins, where zap still wins, and how to move incrementally without a big-bang rewrite.</description>
    </item>
  </channel>
</rss>
