>Hah. Voldemort types. The ones that can't be named Ha ha, that reminds me of that phrase of yore, "the quality without a name (qwan)" (google it), which was h

>Hah. Voldemort types. The ones that can't be named Ha ha, that reminds me of that phrase of yore, "the quality without a name (qwan)" (google it), which was heavily bandied about years ago, during the heyday of C++ and the software patterns movement (which continued a lot in the days of Java, of course). James Coplien (IIRC) and others of that time come to mind. https://en.m.wikipedia.org/wiki/The_Timeless_Way_of_Building https://en.m.wikipedia.org/wiki/The_Timeless_Way_of_Building https://en.m.wikipedia.org/wiki/Pattern_language https://en.m.wikipedia.org/wiki/Pattern_language https://en.m.wikipedia.org/wiki/Jim_Coplien https://en.m.wikipedia.org/wiki/Jim_Coplien Though I read a fair amount about that stuff, a lot of of it went over my head, but later, I did understand some of the patterns, after reading the design patterns book, and trying out some of them. The template method pattern is my favourite pattern, because I understand it more well than many of the others :), and also because it is the basis of software frameworks (inversion of control, aka the Hollywood principle - "don't call me, I'll call you"). Other patterns that I like and understand are the command pattern, the interpreter pattern, the chain of responsibility pattern, and flyweight pattern, to name a few. Builder and Factory, not so much. Singleton is straightforward, or is it really? impls matter :) And I have written a few toy frameworks, which is fun to do and use.