<?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>Domain Driven Design on Noggin</title><link>https://noggin.vedant-ships.in/tags/domain-driven-design/</link><description>Recent content in Domain Driven Design on Noggin</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 26 Feb 2023 16:02:07 +0530</lastBuildDate><atom:link href="https://noggin.vedant-ships.in/tags/domain-driven-design/index.xml" rel="self" type="application/rss+xml"/><item><title>A dummy's encounter with Domain Driven Design</title><link>https://noggin.vedant-ships.in/posts/ddd-encounter/</link><pubDate>Sun, 26 Feb 2023 16:02:07 +0530</pubDate><guid>https://noggin.vedant-ships.in/posts/ddd-encounter/</guid><description>&lt;p&gt;As a software developer, I had vaguely heard of the term &amp;ldquo;Domain Driven Design&amp;rdquo; thrown around in my office circle, but I never completely understood what exactly it is.
In my quest to figure out what it was, I uncovered a &lt;a href="https://youtu.be/pMuiVlnGqjk"&gt;video&lt;/a&gt; on YouTube by Eric Evans, who also basically came up with this concept in &lt;a href="https://www.amazon.in/Domain-Driven-Design-Tackling-Complexity-Software/dp/0321125215"&gt;one of his books&lt;/a&gt;.
This post is my attempt to list my takeaways from this video and my opinions on Domain Driven Design in general.&lt;/p&gt;</description></item></channel></rss>