It's an easily digestable resource with clear examples. I'd forward it to our junior engineers. Something irked me about this sentence though: > I contend that

It's an easily digestable resource with clear examples. I'd forward it to our junior engineers. Something irked me about this sentence though: > I contend that these three axes: colocation, domain interdependence, and practical interdependence, form a basis that covers Coupling, Cohesion, DRYness, and the Wrong Abstraction, as well as some other things too. Seeing as the author is mainly rehashing themes from the GoF book, albeit with more modern examples (e.g microservices and npm dependencies), I would maybe phrase that a bit more humbly. To me, Wrong Abstraction is just the Single Responsibility Principle stated differently (which the author doesn't mention - not even as Separation of Concerns). _I contend_ that one could derive all other rules and patterns from this one principle.