To tell the truth, this isn't a subject that I particularly like. But I do feel there's a need for this to be written about. Right now, when the subject of…
I'll write up a more thorough description of why I think so, but for now let's just say that the book is doing more harm than good to people who read it without a lot of caution. An interesting reference to notice in this regard could be Page 10 of this presentation by Peter Norvig in which he presents the result of a study of the classic GoF Design Patterns book's applicability to a dynamic language such as Lisp or Dylan. His study concludes:
16 of 23 patterns are either invisible or simpler
So, it is this that compels me to try to write about the subject. And I think it will also be this one of the guiding basis for writing: Trying to avoid doing harm. It is for this reason that I can't really, truly, sincerely promise I will actually get to the task, at least in a prompt manner. This will take thought. It will also surely need help from others, which I don't know if I'll be able to get.
In any case, I do hope that this turns out to be, at least, a good place for conversation with those interested in actually having a reference that can actually be regarded as more correct than not.
Who this is for
This will be focused on design patterns and general principles. There is no intention to study or cover any detail of any particular code-base. While it may happen that some concrete code found in the wild could be pointed as an example implementation, this will be just as example.
In this regard, I, flynn here, do not consider myself to be particularly knowledgeable or well suited to the task and this will probably be as much a learning experience for me as for anyone else. But at least I will try to get to the goal.
Content so far
- Design Patterns: A brief introduction/definition of what we're talking about.
- a page to share proposals on patterns to analyse and discuss about their merits.
- First basic draft on the command non-pattern.