<?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>Development on Musings about technology</title><link>https://sirile.github.io/tags/development/</link><description>Recent content in Development on Musings about technology</description><generator>Hugo -- 0.157.0</generator><language>en-us</language><lastBuildDate>Wed, 08 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sirile.github.io/tags/development/index.xml" rel="self" type="application/rss+xml"/><item><title>Dialogue driven development: when code becomes the documentation</title><link>https://sirile.github.io/posts/2026-04-08-dialogue-driven-development/</link><pubDate>Wed, 08 Apr 2026 00:00:00 +0000</pubDate><guid>https://sirile.github.io/posts/2026-04-08-dialogue-driven-development/</guid><description>&lt;p&gt;Twenty-five years ago, extreme programming made a bold promise: code should be the documentation. Good idea. Didn&amp;rsquo;t work. Humans can&amp;rsquo;t efficiently parse 50,000 lines of code to understand what a system does and why. So we kept writing design docs, architecture diagrams, and specification documents – and they kept going stale.&lt;/p&gt;
&lt;p&gt;AI changes that. An agent can read an entire codebase and produce a feature summary that&amp;rsquo;s more accurate than the design doc written six months ago, because it reflects what actually exists. The XP promise is finally landing – just not the way anyone expected.&lt;/p&gt;</description></item></channel></rss>