<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Metaphor on Stack Research</title><link>https://stackresearch.org/tags/metaphor/</link><description>Recent content in Metaphor on Stack Research</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 17 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://stackresearch.org/tags/metaphor/index.xml" rel="self" type="application/rss+xml"/><item><title>Executable Metaphors: Compiling Analogy Into Prototype Code</title><link>https://stackresearch.org/research/executable-metaphors/</link><pubDate>Tue, 17 Mar 2026 00:00:00 +0000</pubDate><guid>https://stackresearch.org/research/executable-metaphors/</guid><description>&lt;p&gt;Metaphors already shape software.&lt;/p&gt;
&lt;p&gt;A pipeline moves data from one stage to another. Garbage collection reclaims unused memory. A queue holds work until something is ready to process it. These words are not decorative. They carry a small model of how a system should behave.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/stack-research/executable-metaphors"&gt;Executable Metaphors&lt;/a&gt; asks what happens if that model becomes the input to a compiler. A short analogy, written in Markdown, is treated as the source artifact. The generated code, build files, documentation, and repair scripts are outputs.&lt;/p&gt;</description></item></channel></rss>