I think I am becoming a design
patterns agnostic. I want to believe in them, but am not sure how to get the benefit. I'm finding I re-use techniques I've seen and found useful. These may come from a simplistic example of a design pattern. But at some point, "making pizza" examples only go so far in aiding my understanding of what role the design pattern has in the real world. I've been helped a lot the few times I've seen discussions of- when encountering this problem- these strategies might be helpful for these reasons.
What is the approach of your book? Does agnostic mean higher level concepts, or focusing on problem types? How do you illustrate the use of a design pattern if you are trying to avoid any specific language implementation? Do you contrast different approaches that may be applicable to the same problem?