<?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>Part-Iv on communities.abhinav-ja.in</title><link>https://communities.abhinav-ja.in/tags/part-iv/</link><description>Recent content in Part-Iv on communities.abhinav-ja.in</description><generator>Hugo -- 0.137.1</generator><language>en</language><lastBuildDate>Sun, 31 Aug 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://communities.abhinav-ja.in/tags/part-iv/index.xml" rel="self" type="application/rss+xml"/><item><title>Week 17 – Bringing the Strategy Together</title><link>https://communities.abhinav-ja.in/book-club/domain-driven-design/week-17/</link><pubDate>Sun, 31 Aug 2025 00:00:00 +0000</pubDate><guid>https://communities.abhinav-ja.in/book-club/domain-driven-design/week-17/</guid><description>&lt;p>This week we&amp;rsquo;ll discuss the last chapter of the book: &lt;strong>Chapter 17 – Bringing the Strategy Together&lt;/strong>.&lt;/p>
&lt;p>We&amp;rsquo;ve reached the end. It&amp;rsquo;s been a long and often arduous few months reading this book, but I&amp;rsquo;ve genuinely enjoyed sharing the ride with this bunch. I&amp;rsquo;ll write a final note in a couple of days about how much this experience has shifted my thinking, but for now, let&amp;rsquo;s dive into the last chapter.&lt;/p></description></item><item><title>Week 16 – Large-Scale Structure</title><link>https://communities.abhinav-ja.in/book-club/domain-driven-design/week-16/</link><pubDate>Sun, 24 Aug 2025 00:00:00 +0000</pubDate><guid>https://communities.abhinav-ja.in/book-club/domain-driven-design/week-16/</guid><description>&lt;p>This week we&amp;rsquo;ll discuss the &lt;strong>second last chapter&lt;/strong> of the book, &lt;strong>Chapter 16: Large-Scale Structure&lt;/strong>. This chapter was more about holding a sprawling system together when the model grows big than anything else. And it does get big — even when you&amp;rsquo;ve done everything &amp;ldquo;right.&amp;rdquo;&lt;/p>
&lt;p>I liked the satellite communication simulator example that opens the chapter. The team had a solid model, modular design, and good abstractions but it still started falling apart at scale. That resonated. Sometimes things drift not because they&amp;rsquo;re badly built, but because they&amp;rsquo;re not built with a larger shape in mind.&lt;/p></description></item><item><title>Week 14 &amp; 15 – Maintaining Model Integrity / Distillation</title><link>https://communities.abhinav-ja.in/book-club/domain-driven-design/week-14/</link><pubDate>Sun, 17 Aug 2025 00:00:00 +0000</pubDate><guid>https://communities.abhinav-ja.in/book-club/domain-driven-design/week-14/</guid><description>&lt;p>Apologies for not posting the Week 14 thread last week. We had a mix-up with scheduling and a couple of us were catching up on reading. Given that the two chapters flow nicely into each other, it worked out okay to talk about them together.&lt;/p>
&lt;h2 id="chapter-14--maintaining-model-integrity">Chapter 14 – Maintaining Model Integrity&lt;/h2>
&lt;p>This chapter was more tactical than philosophical, which made for a slightly different reading pace. It dives into the patterns for preserving the integrity of large systems by managing how different models interact. I found the distinction between &lt;strong>Shared Kernel&lt;/strong> and &lt;strong>Customer/Supplier&lt;/strong> particularly useful — one speaks to tight alignment, the other to necessary detachment. The &lt;strong>&amp;ldquo;Conformist&amp;rdquo;&lt;/strong> pattern also stood out, not because it&amp;rsquo;s ideal, but because it acknowledges the reality of working with upstream teams that you have no leverage over.&lt;/p></description></item></channel></rss>