Re: A few questions about singletons...
On Sep 28, 8:15 am, Krice <pau...@mbnet.fi> wrote:
On 25 syys, 20:44, Noah Roberts <d...@reply.com> wrote:
Patterns ARE central to solid development.
Patterns are like templates, they have become a trend
that everyone has to use, even there is no reason.
Patterns are totally unlike templates; they aren't so much a
software development technique per se, as a means of
communication (including communicating with yourself). And
until someone suggests something better... Communication is
essential to well written programs, and using a recognized
pattern make the code far easier to understand (and thus more
likely correct) than it would be if you reinvented the wheel
each time around.
Note that in any real program, there will be lots of use of
patterns. I've never seen a GUI interface that didn't use at
least one of the template method pattern, the strategy pattern
or the decorator pattern. (Most will use all of them at
different points.) So the real question is: does the
documentation just say that such and such a pattern is used, or
does the documentation describe all of the nitty gritty details
each time, leaving the client wondering if somewhere in the
three or four pages of documentation, there isn't a subtle
difference in the pattern this time around.