<?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>Developer Experience on Severin Bucher | Blog</title><link>https://severinbucher.com/tags/developer-experience/</link><description>Recent content in Developer Experience on Severin Bucher | Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 25 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://severinbucher.com/tags/developer-experience/index.xml" rel="self" type="application/rss+xml"/><item><title>The Architecture of Boring Tooling</title><link>https://severinbucher.com/posts/the-architecture-of-boring-tooling/</link><pubDate>Tue, 25 Aug 2026 00:00:00 +0000</pubDate><guid>https://severinbucher.com/posts/the-architecture-of-boring-tooling/</guid><description>&lt;p>The best toolchains share a common property: they make the default workflow easy, predictable, and boring. They shift entire classes of errors from production toward compile time and local feedback.&lt;/p>
&lt;p>Good tooling relocates inherent system complexity to an earlier, cheaper, and more deterministic phase of the development lifecycle.&lt;/p>
&lt;p>When a toolchain succeeds, these effects compound: fewer decisions to make, more visible structure, earlier errors, enforceable boundaries, faster feedback. Developer attention stays on the product.&lt;/p></description></item></channel></rss>