<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Eip on Hullabalooing</title>
    <link>https://cruver.ai/tags/eip/</link>
    <description>Recent content in Eip on Hullabalooing</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 26 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://cruver.ai/tags/eip/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Greenspun&#39;s Tenth Rule for Integration</title>
      <link>https://cruver.ai/writing/posts/greenspun-eip/</link>
      <pubDate>Tue, 26 May 2026 00:00:00 +0000</pubDate>
      <guid>https://cruver.ai/writing/posts/greenspun-eip/</guid>
      <description>&lt;p&gt;&lt;em&gt;I wrote a &lt;a href=&#34;https://hullabalooing.cruver.ai/writing/posts/keip-eip-ai-kubernetes/&#34;&gt;previous post&lt;/a&gt; about applying these EIPs concretely on Kubernetes for AI orchestration. That post answers &amp;ldquo;how&amp;rdquo;; this one is the &amp;ldquo;why you should care&amp;rdquo; piece that should have come before it.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;Philip Greenspun, writing about Lisp in the mid-1990s, formulated what came to be called his Tenth Rule: any sufficiently complicated C or Fortran program contains an ad-hoc, informally specified, bug-ridden, slow implementation of half of Common Lisp. His point has aged well. Programs grow; the things they need to express grow with them; absent a richer substrate, the missing pieces get reinvented in the language at hand, typically badly.&lt;/p&gt;</description>
    </item>
    <item>
      <title>I Built an AI Video Pipeline. It&#39;s Mostly Enterprise Integration Patterns.</title>
      <link>https://cruver.ai/writing/posts/ai-video-pipeline-eip/</link>
      <pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate>
      <guid>https://cruver.ai/writing/posts/ai-video-pipeline-eip/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve spent the last few weeks building a documentary video generation pipeline. A topic goes in (say: &amp;ldquo;Sankebetsu brown bear incident 1915 Hokkaido&amp;rdquo;) and a finished mp4 comes out (a ten-minute narrated documentary, 27 scenes, original visuals, voiced by a documentary-grade TTS), all running on a homelab cluster.&lt;/p&gt;&#xA;&lt;p&gt;Between those two endpoints sits a chain of eight passes that hand off to each other. Several fan out to &amp;ldquo;do N things in parallel and aggregate.&amp;rdquo; Several produce artifacts measured in MB per scene that should not be shoved through a message broker. A few are the right place to put a human in the loop, where one minute of editorial review saves hours of GPU time downstream.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
