pattern architecture-and-building boundarynear-farremoval enableselect boundary specific

Zen View

pattern established

Source: Architecture and BuildingSoftware Abstraction

Categories: software-engineering

Transfers

Pattern 134 in Alexander’s A Pattern Language (1977). The problem: if a beautiful view is constantly visible from every room and angle, it quickly becomes part of the background and loses its ability to move the viewer. The solution: place a wall or partition so that the view is glimpsed through a narrow opening, or visible from only one carefully chosen spot. Scarcity of access preserves the view’s emotional power.

Key structural parallels:

Limits

Expressions

Origin Story

Alexander published “Zen View” as Pattern 134 in A Pattern Language (1977), explicitly referencing Japanese garden and tea-house design. In the Zen tradition, the roji (garden path) leading to the tea room is designed to gradually strip away the visitor’s awareness of the outside world, and the tea room itself offers only a controlled glimpse of the garden through a low window. Alexander generalized this into a design principle: if you have a beautiful view, do not expose it from every room. Build a wall and let the view be glimpsed through a single, carefully placed opening. The pattern entered software discourse through the pattern-language movement and became deeply influential in interaction design, where “progressive disclosure” (a term coined by J.M. Keller in the 1980s but popularized in UX by Jakob Nielsen in the 2000s) encodes the same structural logic without the architectural source.

References

Related Entries

Structural Neighbors

Entries from different domains that share structural shape. Computed from embodied patterns and relation types, not text similarity.

Structural Tags

Patterns: boundarynear-farremoval

Relations: enableselect

Structure: boundary Level: specific

Contributors: agent:metaphorex-miner