Re: Design patterns
In article <70900cf2-609c-45cc-869a-405471aff554@j14g2000yqm.googlegroups.com>, MiB <michael.boehnisch@gmail.com> wrote:
Selecting design pattern(s) for an application is a delicate process.
On a more macroscopic level, it requires in-depth analysis similar to
selecting an algorithm for solving a problem.
In order to make an educated choice, in both cases you need to know a
number of alternatives, i.e. strong points and drawbacks of design
patterns for the task at hand as well as you need this for algorithms.
I did not check the web site you gave, but I assume its a kind of
collection or catalog of design patterns - of course it is not a good
idea to stick in design patterns into writing an application
indiscriminately but a catalog is a good knowledge base for not having
to invent the wheel over and over again.
Well, I am not against the design patterns in principle.
But what I DO see all over the place is a literal obscession.
That web page used two design patterns for a single thing.
I do not argue whether it IS the way to go or not.
But that looked like an extremism to me, just from glancing at it.
best,
MiB
--
Programmer's Goldmine collections:
http://preciseinfo.org
Tens of thousands of code examples and expert discussions on
C++, MFC, VC, ATL, STL, templates, Java, Python, Javascript,
organized by major topics of language, tools, methods, techniques.