<?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>Posts on The Practical AI Builder</title>
    <link>https://aitechy226.github.io/posts/</link>
    <description>Recent content in Posts on The Practical AI Builder</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 10 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://aitechy226.github.io/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>GPU Infrastructure: The Five Calculations That Actually Matter</title>
      <link>https://aitechy226.github.io/posts/gpu-infrastructure-five-calculations/</link>
      <pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://aitechy226.github.io/posts/gpu-infrastructure-five-calculations/</guid>
      <description>VRAM fit, quantization impact, multi-node thresholds, egress cost, and real TCO — the five calculations that determine whether a GPU deployment actually works.</description>
    </item>
    <item>
      <title>The Trust Layer: What Separates Good RAG from Enterprise RAG</title>
      <link>https://aitechy226.github.io/posts/enterprise-rag-trust-layer/</link>
      <pubDate>Wed, 08 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://aitechy226.github.io/posts/enterprise-rag-trust-layer/</guid>
      <description>Four bugs found while hardening a RAG system for FSI and life sciences — and what they reveal about the gap between a working system and a trustworthy one.</description>
    </item>
    <item>
      <title>The AI PC Buying Problem Every Enterprise Needs to Solve</title>
      <link>https://aitechy226.github.io/posts/benchmarking-ai-devices/</link>
      <pubDate>Sun, 05 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://aitechy226.github.io/posts/benchmarking-ai-devices/</guid>
      <description>The vendor numbers are real. The benchmarks are valid. And the procurement question still does not have a clean answer — here is the gap I kept running into.</description>
    </item>
    <item>
      <title>MCP in Production, Part 1: Persistent Sessions, Pooling, and Fault Tolerance</title>
      <link>https://aitechy226.github.io/posts/mcp-production-part-1/</link>
      <pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://aitechy226.github.io/posts/mcp-production-part-1/</guid>
      <description>Five transport-layer decisions — session pooling, eviction, cancel scope isolation, timeouts, and heartbeat design — each driven by a real failure in a KYC onboarding system.</description>
    </item>
    <item>
      <title>MCP in Production, Part 2: Authentication, Observability, and Operational Design</title>
      <link>https://aitechy226.github.io/posts/mcp-production-part-2/</link>
      <pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://aitechy226.github.io/posts/mcp-production-part-2/</guid>
      <description>Bearer token auth at the transport layer, correlation IDs across four servers, lazy session init, and clean shutdown — the system-level decisions that make an MCP client deployable.</description>
    </item>
    <item>
      <title>Designing a Professional Digital Twin: The Architecture</title>
      <link>https://aitechy226.github.io/posts/professional-digital-twin/</link>
      <pubDate>Tue, 31 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://aitechy226.github.io/posts/professional-digital-twin/</guid>
      <description>Most professional knowledge lives in people&amp;#39;s heads. Here&amp;#39;s what it looks like when you structure it as an agentic system — personas, tools, skills, rules, and memory.</description>
    </item>
    <item>
      <title>I Used MCP as a Service-to-Service Protocol. Here&#39;s What I Learned.</title>
      <link>https://aitechy226.github.io/posts/mcp-service-to-service/</link>
      <pubDate>Tue, 31 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://aitechy226.github.io/posts/mcp-service-to-service/</guid>
      <description>MCP was designed as an LLM-to-tool protocol. I used it as a service-to-service layer between a LangGraph orchestrator and independently deployable integration servers. It worked — with real tradeoffs.</description>
    </item>
    <item>
      <title>Why Your AI Agent Demo Looks Great and Your Production System Doesn&#39;t</title>
      <link>https://aitechy226.github.io/posts/agentic-hype-vs-reality/</link>
      <pubDate>Tue, 31 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://aitechy226.github.io/posts/agentic-hype-vs-reality/</guid>
      <description>A practitioner&amp;#39;s take on the gap between agentic hype and agentic reality.</description>
    </item>
  </channel>
</rss>
