I’m still going back to the “Class” Pattern in C. You’re creating structs and typedefs when what you really need are classes. It’s almost as if I’m breaking the DRY principle by doing the same things over and over again. Wouldn’t it be cool if you could just create a “factory pattern” class that you could reuse?

I want to read Analysis Patterns by Martin Fowler, but it isn’t available here.

Also, in your point on why patterns are more like frameworks for solutions, rather than solutions themselves… I think that they are more portable this way, and are generic so that they may gain more usage. No one solution will work for all types of software, but the community has extracted (as computer scientists do so well) a common set of tools that anyone can use (or not use) in their designs.

You should read Analysis Patterns by Martin Fowler. It supplies more concrete solutions to typical software problems. It suggests an object model and interaction techniques for health care, insurance, and a few others.