<?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>Model-Driven-Design on communities.abhinav-ja.in</title><link>https://communities.abhinav-ja.in/tags/model-driven-design/</link><description>Recent content in Model-Driven-Design on communities.abhinav-ja.in</description><generator>Hugo -- 0.137.1</generator><language>en</language><lastBuildDate>Sun, 25 May 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://communities.abhinav-ja.in/tags/model-driven-design/index.xml" rel="self" type="application/rss+xml"/><item><title>Week 3 – Binding Model and Implementation</title><link>https://communities.abhinav-ja.in/book-club/domain-driven-design/week-03/</link><pubDate>Sun, 25 May 2025 00:00:00 +0000</pubDate><guid>https://communities.abhinav-ja.in/book-club/domain-driven-design/week-03/</guid><description>&lt;p>Opening the thread for &lt;strong>Chapter 3 – Binding Model and Implementation&lt;/strong>.&lt;/p>
&lt;p>I found this chapter a bit difficult initially, maybe due to all the electronics references. After reading it a couple of times, I understood that this chapter could honestly be replaced by a single line: &lt;strong>&amp;ldquo;Software development is all design.&amp;rdquo;&lt;/strong>&lt;/p>
&lt;p>It really takes off from where the last chapter left — if ubiquitous language was about getting everyone (developers and domain experts) to speak the same language, this one goes a step further: not just speak the same way, but design the same way.&lt;/p></description></item></channel></rss>