<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>obuchmann.dev</title><link>https://obuchmann.dev/</link><description>Recent content on obuchmann.dev</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 07 Jul 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://obuchmann.dev/index.xml" rel="self" type="application/rss+xml"/><item><title>Distribution Is Not Federation</title><link>https://obuchmann.dev/posts/distribution-is-not-federation/</link><pubDate>Tue, 07 Jul 2026 00:00:00 +0200</pubDate><guid>https://obuchmann.dev/posts/distribution-is-not-federation/</guid><description>&lt;p>&lt;a href="https://martinfowler.com/articles/harness-engineering.html">Birgitta Böckeler&amp;rsquo;s article on harness engineering&lt;/a> — the practice of wrapping a model in the guides, sensors, and feedback loops that make it a reliable coding agent — leaves one question deliberately open. Harness templates, she notes, could let larger organizations share common guides and sensors — but the moment a team instantiates a template, it starts drifting out of sync. The versioning and contribution problems might be &lt;em>worse&lt;/em> than with classic service templates, because guides and sensors are not deterministic artifacts. She names the problem and moves on.&lt;/p></description></item></channel></rss>