Pearl language

From Pearl Language
Revision as of 08:01, 24 April 2014 by Martien (talk | contribs) (Background++)
Jump to navigation Jump to search

…{{{context}}}

✣  ✣  ✣

{{{wish full}}}

Similar to A Pattern Language—Towns • Buildings • Construction by Christopher Alexander, Sara Ishikawa, Murray Silverstein, but with a twist: it describes the goal or wish rather than the problem. In other words, it focuses on the positive opposite of a problem.

Therefore:

{{{therefore full}}}

✣  ✣  ✣



✣  ✣  ✣

Reality tends to force tradeoffs between seemingly conflicting goals, such as flexibility and maintainability against size and complexity.

A pearl facilitates these tradeoffs by documenting a well​working approach to fulfill a desire or wish that occurs repeatedly in a given context.

Applying a pearl in a given context results in a new, changed context that, in turn, solicits new pearls to make it more whole.

pearls evolve during a highly collaborative style based on “shepherding” before submission and peer-based feedback writer’s workshop.

pearls neither fulfill all desires, nor replace design skills or solve all problems.

Well crafted pearls provide valuable nuggets of relevant advice based on actual experience. Learning by doing—learning from experiments and making mistakes—often isn’t an option for real world projects, so pearls can provide a way to learn from others’ experience and mistakes.

The Timeless Way of Building by Christopher Alexander clarifies that “the pattern [or pearl] is, in short, at the same time a thing, which happens in the world, and the rule which tells us how to create that thing, and when we must create it.” pearls present a reusable solution, provide information about its usefulness and tradeoffs, and encapsulate knowledge about proven practices.

Sources