<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Domain-Driven-Design on Yushi's Blog</title><link>https://blog.yushi91.com/blog/domain-driven-design/</link><description>Recent content in Domain-Driven-Design on Yushi's Blog</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright © 2025, Yushi Cui.</copyright><lastBuildDate>Tue, 16 Jun 2026 10:00:00 +1200</lastBuildDate><atom:link href="https://blog.yushi91.com/blog/domain-driven-design/index.xml" rel="self" type="application/rss+xml"/><item><title>DDD Was the Acronym I Ignored, Until Agents Made Me Care</title><link>https://blog.yushi91.com/blog/domain-driven-design-glossary-for-agents/</link><pubDate>Tue, 16 Jun 2026 10:00:00 +1200</pubDate><guid>https://blog.yushi91.com/blog/domain-driven-design-glossary-for-agents/</guid><description>&lt;p&gt;&lt;img src="https://blog.yushi91.com/domain-driven-design-glossary-for-agents.webp" alt="DDD and the shared glossary for agents" loading="lazy"&gt;
&lt;/p&gt;
&lt;h2 id="the-acronym-i-waved-off"&gt;The acronym I waved off&lt;/h2&gt;
&lt;p&gt;I&amp;rsquo;m comfortable with a few of the development acronyms. TDD, test-driven development, I use. BDD, behaviour-driven development, I understand. But DDD, domain-driven design, was always the one I let slide past me.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;d seen the term before. I knew it existed. I just never paid attention, because from a distance it looked like it was only about agreeing on vocabulary with your dev team or your product team. Defining glossary terms. Naming things consistently.&lt;/p&gt;</description></item></channel></rss>