> Usually the work crosses several layers in at least one place You are doing it wrong then. It's basically a violation of SRP. Your changes should touch only

> Usually the work crosses several layers in at least one place You are doing it wrong then. It's basically a violation of SRP. Your changes should touch only one layer. If it's not, you have fragile abstractions. I agree there are a number of cases when you introduce a new thing you should thread implementation through all layers. But not for maintenance and bugs (common case). > Too much "clean code" will make a single layer no longer fit in working memory even at an "overview" level. But why you need to keep it in memory? Do you keep all OS APIs? Or standard library? They are other layers you use and have no issues with broad interface. Your application layers is the same thing.