<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Olinske</title>
    <link>https://zach.olinski.com/</link>
    <description>Signal over hype for enterprise AI, cloud resilience, and CTO operating models.</description>
    <language>en-us</language>
    <item>
      <title>BCDR for Azure Storage: Patterns That Actually Hold</title>
      <link>https://zach.olinski.com/posts/000006-bcdr-azure-storage-patterns/</link>
      <guid isPermaLink="true">https://zach.olinski.com/posts/000006-bcdr-azure-storage-patterns/</guid>
      <description>Enterprise backup, continuity, and disaster recovery for Azure Storage requires multi-region strategy, validation testing, and clear automation boundaries. Here is what works.</description>
      <pubDate>Thu, 14 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Building Multi-Agent Solutions Without Making a Mess</title>
      <link>https://zach.olinski.com/posts/000005-multi-agent-solutions-architecture/</link>
      <guid isPermaLink="true">https://zach.olinski.com/posts/000005-multi-agent-solutions-architecture/</guid>
      <description>Teams deploying multiple AI agents face coordination, state management, and failure propagation problems. Here is what actually works in production.</description>
      <pubDate>Sun, 10 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Azure AI Foundry: When Capacity Scarcity Pushes Customers into PTU Too Early</title>
      <link>https://zach.olinski.com/posts/000004-ptu-vs-tpm-azure-ai-foundry/</link>
      <guid isPermaLink="true">https://zach.olinski.com/posts/000004-ptu-vs-tpm-azure-ai-foundry/</guid>
      <description>When Standard capacity is constrained, enterprises may move to provisioned throughput before demand is proven. That can create stranded cost and reduce cloud elasticity in practice.</description>
      <pubDate>Wed, 06 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>AI Agent Governance: A Starting Point Nobody Gave Me</title>
      <link>https://zach.olinski.com/posts/ai-agent-governance-starting-point/</link>
      <guid isPermaLink="true">https://zach.olinski.com/posts/ai-agent-governance-starting-point/</guid>
      <description>My LinkedIn automation posted a draft with a broken link before I knew it happened. People commented. The blog had never published it. That is when I realized my agent pipeline had no governance. Here is what I built after that mistake.</description>
      <pubDate>Wed, 29 Apr 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>100 Drafts and Nothing Published. Can AI Solve the Problem That Is Me?</title>
      <link>https://zach.olinski.com/posts/100-drafts-nothing-published-can-ai-solve-me/</link>
      <guid isPermaLink="true">https://zach.olinski.com/posts/100-drafts-nothing-published-can-ai-solve-me/</guid>
      <description>I had 100 blog posts stuck in draft on WordPress and 50 more on the new platform. The problem was never the tools. It was me. So I built an editing team out of AI agents to find out if that changes anything.</description>
      <pubDate>Sun, 19 Apr 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Why CTOs Need to Mandate Architecture Decision Records</title>
      <link>https://zach.olinski.com/posts/000008-architecture-decision-records-cto/</link>
      <guid isPermaLink="true">https://zach.olinski.com/posts/000008-architecture-decision-records-cto/</guid>
      <description>Architecture Decision Records (ADRs) are not bureaucracy. They are the only scalable way to preserve context and prevent repeated mistakes as teams grow.</description>
      <pubDate>Sun, 12 Apr 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Welcome to Signal Over Hype</title>
      <link>https://zach.olinski.com/posts/000001-welcome/</link>
      <guid isPermaLink="true">https://zach.olinski.com/posts/000001-welcome/</guid>
      <description>Why I started writing, what I will cover, and what to expect.</description>
      <pubDate>Sat, 28 Mar 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>