<?xml version='1.0' encoding='utf-8'?>
<rss version="2.0">
  <channel>
    <title>argakiig blog</title>
    <link>https://blog.argakiig.xyz/</link>
    <description>Notes on distributed systems, infrastructure, and production engineering.</description>
    <language>en-us</language>
    <lastBuildDate>Tue, 02 Jun 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>The Most Dangerous Engineer</title>
      <link>https://blog.argakiig.xyz/posts/the-most-dangerous-engineer/</link>
      <guid>https://blog.argakiig.xyz/posts/the-most-dangerous-engineer/</guid>
      <pubDate>Tue, 02 Jun 2026 00:00:00 GMT</pubDate>
      <description>The most dangerous engineer on a team isn't the junior. It's the one who stopped being curious, because everything underneath them keeps moving whether they keep learning or not.</description>
    </item>
    <item>
      <title>Distributed Systems Are Mostly Apologies</title>
      <link>https://blog.argakiig.xyz/posts/distributed-systems-are-mostly-apologies/</link>
      <guid>https://blog.argakiig.xyz/posts/distributed-systems-are-mostly-apologies/</guid>
      <pubDate>Mon, 01 Jun 2026 00:00:00 GMT</pubDate>
      <description>A distributed system is a collection of carefully managed disappointments. The engineering isn't avoiding failure, it's choosing which failures you're willing to tolerate.</description>
    </item>
    <item>
      <title>The Code Looks Fine. That's the Problem.</title>
      <link>https://blog.argakiig.xyz/posts/the-review-moved-up-the-stack/</link>
      <guid>https://blog.argakiig.xyz/posts/the-review-moved-up-the-stack/</guid>
      <pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate>
      <description>AI made the obvious mistakes rare and the expensive ones invisible. Code review didn't get easier. It moved up the stack, from implementation to judgment.</description>
    </item>
    <item>
      <title>"It Works" Is Not "It's Ready"</title>
      <link>https://blog.argakiig.xyz/posts/it-works-is-not-ready/</link>
      <guid>https://blog.argakiig.xyz/posts/it-works-is-not-ready/</guid>
      <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
      <description>AI is great at getting an app running. It is not the same as getting it ready for real users, real payments, and real data. Here is where the gap hides.</description>
    </item>
    <item>
      <title>AI Is a Tool — Nothing More, Nothing Less</title>
      <link>https://blog.argakiig.xyz/posts/ai-is-a-tool/</link>
      <guid>https://blog.argakiig.xyz/posts/ai-is-a-tool/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description>AI is another abstraction in a long line of them. The real question was never whether engineers use it, but whether they understand what they ship.</description>
    </item>
    <item>
      <title>Realtime Recovery, Part 4 — The Operational Reality</title>
      <link>https://blog.argakiig.xyz/posts/the-operational-reality/</link>
      <guid>https://blog.argakiig.xyz/posts/the-operational-reality/</guid>
      <pubDate>Fri, 22 May 2026 00:00:00 GMT</pubDate>
      <description>Replay storms, cost amplification, cache pressure, and backpressure — what makes a recovery design survive contact with production.</description>
    </item>
    <item>
      <title>Realtime Recovery, Part 3 — Replay Without Stopping Live Traffic</title>
      <link>https://blog.argakiig.xyz/posts/replay-without-stopping-live-traffic/</link>
      <guid>https://blog.argakiig.xyz/posts/replay-without-stopping-live-traffic/</guid>
      <pubDate>Thu, 21 May 2026 00:00:00 GMT</pubDate>
      <description>Idempotent writes, versioned aggregates, and DO NOTHING vs DO UPDATE — merging historical replay into live state without a maintenance window.</description>
    </item>
    <item>
      <title>Realtime Recovery, Part 2 — Watermarks and Intentional Lag</title>
      <link>https://blog.argakiig.xyz/posts/watermarks-and-intentional-lag/</link>
      <guid>https://blog.argakiig.xyz/posts/watermarks-and-intentional-lag/</guid>
      <pubDate>Wed, 20 May 2026 00:00:00 GMT</pubDate>
      <description>Keep collecting in realtime, but finalize behind the present. A lagged watermark is what buys you deterministic replay.</description>
    </item>
    <item>
      <title>Postgres Advisory Locks: What Guarantee Are You Actually Buying?</title>
      <link>https://blog.argakiig.xyz/posts/postgres-advisory-locks/</link>
      <guid>https://blog.argakiig.xyz/posts/postgres-advisory-locks/</guid>
      <pubDate>Wed, 20 May 2026 00:00:00 GMT</pubDate>
      <description>Postgres advisory locks are useful coordination primitives, but they are not durable leadership or consensus.</description>
    </item>
    <item>
      <title>Observability Is Runtime Architecture</title>
      <link>https://blog.argakiig.xyz/posts/observability-is-runtime-architecture/</link>
      <guid>https://blog.argakiig.xyz/posts/observability-is-runtime-architecture/</guid>
      <pubDate>Wed, 20 May 2026 00:00:00 GMT</pubDate>
      <description>Observability is part of runtime architecture, not just a read-only layer over production systems.</description>
    </item>
    <item>
      <title>Realtime Recovery, Part 1 — Recovery Is The System</title>
      <link>https://blog.argakiig.xyz/posts/recovery-is-the-system/</link>
      <guid>https://blog.argakiig.xyz/posts/recovery-is-the-system/</guid>
      <pubDate>Tue, 19 May 2026 00:00:00 GMT</pubDate>
      <description>Live processing is the easy 20% of a streaming system. Deterministic replay is the requirement everything else hangs off of.</description>
    </item>
  </channel>
</rss>