I feel like Fowler typically communicates the "it depends on context, and you need to think on your own" part well. If you haven't read it: I think you'd like

I feel like Fowler typically communicates the "it depends on context, and you need to think on your own" part well. If you haven't read it: I think you'd like the book A Philosophy of Software Design by Ousterhout. It has a very strong notion of what you said and discusses this in a down to earth kind of manner. Very few terms were invented in that book, but it showcases a collection of sensible heuristics and actionable advice.