Continuous Architecture: a Decade of Designing for Change

Principle 4 doesn't seem to make much sense to be included, their section immediately shows that it isn't working in many organisations (to which I can also attest). Perhaps it's better replaced by keeping smaller footprints within the application itself. You know change is coming, you can try to minimise the impact later. Of course just like loosely coupled, that's easier said than done and probably comes with its own caveats.

That was one of the weakest books I read about software. A handful of simple ideas turned around and around in a shallow way. The principles are okish but so generic that you hardly can say anything against them.