I feel like I'm on a different wavelength with Uncle Bob. The majority of my experience has been 1. in the cloud, 2. (micro-)service oriented and 3. using languages that don't require strict OOP. Also, a Software Architect needs to be able to talk about tradeoffs in design, which this book fails to do.

There were some sections that I kind of disagree with. In particular, dismissing the database as a architectural detail feels very optimistic and unrealistic (and almost armchair architect level of consideration, especially considering all of the tradeoff considerations required for distributed datastores). The insight provided by Clean Architecture (TM) was also presented to me early in my career (business logic isolation from data layer and APIs for clients, so that it's inter-operable between different types of clients and datastore), so I can't help but feel like it lacks depth (especially if a junior engineer was able to grasp it so easily).