<?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>Design-Patterns on communities.abhinav-ja.in</title><link>https://communities.abhinav-ja.in/tags/design-patterns/</link><description>Recent content in Design-Patterns on communities.abhinav-ja.in</description><generator>Hugo -- 0.137.1</generator><language>en</language><lastBuildDate>Sun, 27 Jul 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://communities.abhinav-ja.in/tags/design-patterns/index.xml" rel="self" type="application/rss+xml"/><item><title>Week 12 – Relating Design Patterns to the Model</title><link>https://communities.abhinav-ja.in/book-club/domain-driven-design/week-12/</link><pubDate>Sun, 27 Jul 2025 00:00:00 +0000</pubDate><guid>https://communities.abhinav-ja.in/book-club/domain-driven-design/week-12/</guid><description>&lt;p>&lt;em>Discussion led by &lt;strong>Charandeep Kumar&lt;/strong>&lt;/em>&lt;/p>
&lt;hr>
&lt;p>Apologies for the slight delay in getting this thread started — it&amp;rsquo;s been a busy weekend. This week, we&amp;rsquo;re diving into &lt;strong>Chapter 12: Relating Design Patterns to the Model&lt;/strong>.&lt;/p>
&lt;p>For me, this chapter felt like a crucial bridge between the abstract world of domain modeling and the concrete world of implementation patterns we use every day. It addresses a question I think many of us have implicitly wondered about: when is a &amp;ldquo;design pattern&amp;rdquo; just a technical tool, and when does it become a meaningful part of the domain model itself?&lt;/p></description></item></channel></rss>