<?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>YAML on Jaehyeon Kim</title><link>https://jaehyeon.me/tags/yaml/</link><description>Recent content in YAML on Jaehyeon Kim</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © 2023-2026 Jaehyeon Kim. All Rights Reserved.</copyright><lastBuildDate>Tue, 06 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://jaehyeon.me/tags/yaml/index.xml" rel="self" type="application/rss+xml"/><item><title>Defining Data-Streaming Simulations in YAML, Without Writing Python</title><link>https://jaehyeon.me/blog/2026-10-06-simulations-in-yaml-dynamic-des/</link><pubDate>Tue, 06 Oct 2026 00:00:00 +0000</pubDate><guid>https://jaehyeon.me/blog/2026-10-06-simulations-in-yaml-dynamic-des/</guid><description><![CDATA[<p>A pipeline is easier to test when its input behaves like production: orders arrive at random, queues grow, a machine slows down. A simulation can produce that data, but when the simulation is a Python program, every change is a code change. Someone who only wants to double an arrival rate has to read and edit code, and a reviewer has to check that nothing else moved. A file that holds only settings is easier to read, to compare in a pull request and to run in CI.</p>
<p><a href="https://github.com/jaehyeon-kim/dynamic-des" target="_blank" rel="noopener noreferrer">dynamic-des<i class="fas fa-external-link-square-alt ms-1"></i></a> 0.16.0 adds that file. A YAML blueprint describes the whole simulation, and the <code>ddes</code> command runs it. Each of the seven examples in the repository now has a YAML version in plain YAML. The documentation was rebuilt around the three ways to write a simulation.</p>]]></description><enclosure url="https://jaehyeon.me/blog/2026-10-06-simulations-in-yaml-dynamic-des/featured.png" length="798335" type="image/png"/></item></channel></rss>