2005년 10월 22일
Maybe, but patterns are about communicating from one person to
another. If the medium enhances communication with other people it is
good. If it merely makes the machinations of the patterns executable
by a computer it isn't.
set of patterns?
A pattern language is a set of interrelated patterns, all
sharing some of the same context, and perhaps classified into
This term is due to Alexander.
Alexander's use of the term ``language'' is unconventional but
not wrong. If you squint at and overformalize them, pattern
entries are ``production rules''. If you remember your automata
theory, you'll recall that sets of production rules are one way
to characterize recursively enumerable langauges.
Because you haven't written them. If you're interested, you more
than likely know something, and if you know something you can write
Here are some common recommendations:
- Avoid writing about patterns; just
- Pick something you know about and then find multiple
occurrences and/or descriptions. Or conversely, mine
existing software for new possible patterns.
- Find out if other people have written similar patterns
- Aim for quality, not quantity of patterns.
- Figure out why the pattern exists or applies.
- Pick a format for writing about it.
- Circulate it to others (for example, via web pages, patterns
discussion groups, or
submissions to a mailing list) and receive comments.
- Submit it to a vehicle such as PLOP where it can
be reviewed in a writer's workshop.
- Continually iterate and refine.
Some people think there are relatively few undiscovered patterns
that nearly everyone ought to know about. Some people think that there
are a great many more domain-specific patterns that need to be
written. Both may be right. Try writing some more patterns so we can
finding, classifying, indexing, using, and maintaining them?
Probably so. Although if you do, you might no longer be following
much of the method beyond its notation.
In principle, you could be very lucky and have a problem for which
there is already a complete set of patterns, and in which each
application of a pattern flows into the next, leading to a final
product without ever backtracking. But people are never this lucky.
the use of patterns?
Probably so, but even though we discuss it a lot, we don't know
what it is. Use patterns so we can find out.
and software economics?
☞ 내 이글루에 이 글과 관련된 글 쓰기 (트랙백 보내기) [도움말]