This week we’ll discuss the last chapter of the book: Chapter 17 – Bringing the Strategy Together. We’ve reached the end. It’s been a long and often arduous few months reading this book, but I’ve genuinely enjoyed sharing the ride with this bunch. I’ll write a final note in a couple of days about how much this experience has shifted my thinking, but for now, let’s dive into the last chapter. ...
This week we’ll discuss the second last chapter of the book, Chapter 16: Large-Scale Structure. 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’ve done everything “right.” 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’re badly built, but because they’re not built with a larger shape in mind. ...
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. Chapter 14 – Maintaining Model Integrity 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 Shared Kernel and Customer/Supplier particularly useful — one speaks to tight alignment, the other to necessary detachment. The “Conformist” pattern also stood out, not because it’s ideal, but because it acknowledges the reality of working with upstream teams that you have no leverage over. ...