> The purpose of design patterns is to give a name to something you already do, not to find new things that do that aren't needed (cough Spring Framework, J2EE) ... > Now, I'll often make sure to use standard design patterns for my APIs when possible (e.g., Iterator interface, rather than accepting an anonymous classes/function objects if all I want to do let them lazily stream data one at a time).

You're absolutely right. Thanks for catching that!