Refactoring to Patterns is a wonderful book, and it expresses a notion I hold as well, which is that one should be prepared to refactor toward and away from patterns, depending on the situation. I’m paraphrasing here, but the essence of this, to me, was that he was not promot ing the use of patterns in application development as the earmark of good engineering. As an example, he presented a Hello World application, written by some (hopfully) fictitious pattern happy engineer. It gave me a chuckle, as I could see myself as that pattern happy engineer, at one point or another.
The thing to keep in mind is that there is no silver bullet, no shortcut, or easy way (maybe an easiER way). As helpful as patterns and frameworks can be, they can be the source of very painful headaches when in the wrong hands. Picture an abstraction that is orthogonal to the solution plane.