This can lead to another form of anti-pattern. Excessive use of generic patterns can complicate and frustrate code maintenance also. I have seen code-bases whe

This can lead to another form of anti-pattern. Excessive use of generic patterns can complicate and frustrate code maintenance also. I have seen code-bases where these patterns are applied excessively. Generic implementations often take longer to read and understand, and are frequently much more difficult to modify. Adding inheritance can add effort to simple things like code-reviews (the abstract base class is not in the change), and the code cannot be read without jumping between files. My point is not that the template or strategy patterns are bad, but that there is a price to pay. Just use them judiciously.