<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Birdor Engineering — Birdor.dev Engineering</title>
    <link>https://birdor.dev/authors/birdor-engineering</link>
    <description>Engineering records published by Birdor Engineering.</description>
    <language>en</language>
    <lastBuildDate>Tue, 18 Aug 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>MiniX lab review: keeping a multi-host application kernel inspectable</title>
      <link>https://birdor.dev/engineering/minix-multi-host-kernel-review</link>
      <guid isPermaLink="true">https://birdor.dev/engineering/minix-multi-host-kernel-review</guid>
      <description>A public lab review of MiniX: how contracts, controllers, host adapters and manifests create a visible boundary between shared application intent and H5 or WeChat runtime behavior.</description>
      <enclosure url="https://birdor.dev/manus-storage/social-lab-minix-kernel_1e80b700.png" length="0" type="image/png" />
      <pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate>
      <category>Lab Review</category>
      <category>minix</category>
      <category>labs</category>
      <category>typescript</category>
      <category>architecture</category>
      <category>runtime-boundaries</category>
    </item>
    <item>
      <title>PlumeGo lab review: using reference services to test HTTP boundaries</title>
      <link>https://birdor.dev/engineering/plumego-reference-services-review</link>
      <guid isPermaLink="true">https://birdor.dev/engineering/plumego-reference-services-review</guid>
      <description>A public lab review of PlumeGo reference services: how runnable examples and bounded use cases test whether a small Go HTTP kernel remains explicit under application pressure.</description>
      <enclosure url="https://birdor.dev/manus-storage/social-lab-plumego-reference-services_220d1661.png" length="0" type="image/png" />
      <pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate>
      <category>Lab Review</category>
      <category>plumego</category>
      <category>labs</category>
      <category>go</category>
      <category>http</category>
      <category>reference-services</category>
      <category>architecture</category>
    </item>
    <item>
      <title>PlumeGo architecture: explicit Go HTTP boundaries for humans and agents</title>
      <link>https://birdor.dev/engineering/plumego-architecture</link>
      <guid isPermaLink="true">https://birdor.dev/engineering/plumego-architecture</guid>
      <description>How PlumeGo combines a standard-library-only Go kernel, explicit route wiring, stable modules, and machine-readable specifications for inspectable HTTP services.</description>
      <enclosure url="https://birdor.dev/manus-storage/social-plumego-architecture_8254a41c.png" length="0" type="image/png" />
      <pubDate>Sun, 16 Aug 2026 00:00:00 GMT</pubDate>
      <category>Architecture</category>
      <category>plumego</category>
      <category>architecture</category>
      <category>developer-experience</category>
      <category>static</category>
    </item>
    <item>
      <title>Designing system boundaries before service boundaries</title>
      <link>https://birdor.dev/engineering/system-boundaries</link>
      <guid isPermaLink="true">https://birdor.dev/engineering/system-boundaries</guid>
      <description>A practical way to turn an ambiguous product surface into stable technical seams before choosing infrastructure.</description>
      <enclosure url="https://birdor.dev/manus-storage/social-system-boundaries_f10136a4.png" length="0" type="image/png" />
      <pubDate>Sat, 04 Jul 2026 00:00:00 GMT</pubDate>
      <category>Architecture</category>
      <category>architecture</category>
      <category>backend</category>
      <category>decisions</category>
    </item>
    <item>
      <title>Treating engineering content as an interface</title>
      <link>https://birdor.dev/engineering/content-as-interface</link>
      <guid isPermaLink="true">https://birdor.dev/engineering/content-as-interface</guid>
      <description>Why a technical article should expose a stable, useful structure for humans, search systems, and future maintainers.</description>
      <enclosure url="https://birdor.dev/manus-storage/social-content-interface_b32e2e85.png" length="0" type="image/png" />
      <pubDate>Thu, 21 May 2026 00:00:00 GMT</pubDate>
      <category>Engineering Notes</category>
      <category>content</category>
      <category>developer-experience</category>
      <category>documentation</category>
    </item>
    <item>
      <title>Static-first systems for developer-facing sites</title>
      <link>https://birdor.dev/engineering/static-first-web-systems</link>
      <guid isPermaLink="true">https://birdor.dev/engineering/static-first-web-systems</guid>
      <description>How we keep a content-heavy technical surface fast, deployable, and easy to maintain without introducing an application backend.</description>
      <enclosure url="https://birdor.dev/manus-storage/social-static-first_d51a3dd2.png" length="0" type="image/png" />
      <pubDate>Mon, 20 Apr 2026 00:00:00 GMT</pubDate>
      <category>Workflow</category>
      <category>web</category>
      <category>static</category>
      <category>performance</category>
    </item>
    <item>
      <title>Maintaining a small interface as a product scales</title>
      <link>https://birdor.dev/engineering/maintaining-a-small-interface</link>
      <guid isPermaLink="true">https://birdor.dev/engineering/maintaining-a-small-interface</guid>
      <description>A field note on keeping technical surfaces understandable when projects, tools, and experiments begin to multiply.</description>
      <enclosure url="https://birdor.dev/manus-storage/social-small-interface_c8559f2b.png" length="0" type="image/png" />
      <pubDate>Fri, 13 Mar 2026 00:00:00 GMT</pubDate>
      <category>Best Practice</category>
      <category>product-engineering</category>
      <category>interfaces</category>
      <category>maintenance</category>
    </item>
  </channel>
</rss>
