<?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>Entities on communities.abhinav-ja.in</title><link>https://communities.abhinav-ja.in/tags/entities/</link><description>Recent content in Entities on communities.abhinav-ja.in</description><generator>Hugo -- 0.137.1</generator><language>en</language><lastBuildDate>Mon, 09 Jun 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://communities.abhinav-ja.in/tags/entities/index.xml" rel="self" type="application/rss+xml"/><item><title>Week 5 – A Model Expressed in Software</title><link>https://communities.abhinav-ja.in/book-club/domain-driven-design/week-05/</link><pubDate>Mon, 09 Jun 2025 00:00:00 +0000</pubDate><guid>https://communities.abhinav-ja.in/book-club/domain-driven-design/week-05/</guid><description>&lt;p>Apologies for being a day late in starting this thread — the discussion leader for this week had to step away due to unforeseen circumstances, and I&amp;rsquo;ve stepped in to get us back on track. We will be discussing &lt;strong>Chapter 5: A Model Expressed in Software&lt;/strong>.&lt;/p>
&lt;p>This chapter was fairly dense, covering four foundational building blocks of DDD: &lt;strong>Entities, Value Objects, Services, and Modules&lt;/strong>.&lt;/p>
&lt;p>What I appreciated about this chapter is how clearly it lays out the mental categories we need when shaping the model into code. We often throw these terms around, but here Evans gives them weight, tying them to purpose, not just structure.&lt;/p></description></item></channel></rss>