Part-I

Opening the thread for Chapter 3 – Binding Model and Implementation. 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: “Software development is all design.” 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. ...

Opening the thread for Chapter 2 – Communication and the Use of Language. This chapter moves us closer to the interface between language, code, and clarity. Evans argues that the model should not be something floating outside the implementation, rather the best code should reveal the model directly. The diagrams and documents we write should support that, not compete with it. A few lines that stood out: “The vital detail about the design is captured in the code. A well-written implementation should transparently reveal the model underlying it. Supplemental diagrams and documents can guide people’s attention to the central points. Natural language discussion can fill in the nuances of meaning.” ...

Hey folks, Sorry for the late start to the discussion thread this week — I know it doesn’t look great to be late in Week 1, but I imagine most people can empathise with how intense this week has been across the subcontinent. That said, I really enjoyed reading the book. It made me slow down, feel more like myself, and sparked a kind of curiosity I hadn’t felt in a while. ...