To give the building a sense of the delicacy associated with such crafts, as well as a feeling of warmth, I designed louvres from white porcelain panels, and used them to cover the outer walls. The louvres are tapered, to make their tips as fine as possible. (In fact, making tips as thin as possible is one of my key design principles: the thin lip of a teacup allows a better experience of the subtleties of tea - this is always at the forefront of my mind when I pay such close attention to edges.)
An edge is an interface between two mediums. Edges are places of varied ecology. There is hardly a sustainable traditional human settlement that is not sited on those critical junctions of two natural economies. Successful and permanent settlements have always been able to draw from the resources of at least two environments.
Historically, Japan's shrines have been built in order to worship the gods who live in the sacred mountains or seas; They don't reside in the shrine itself, but in the space beyond it. This belief that the spirits and deities exist beyond the confines of the shrine, and that the shrine itself acts not as a centre, but as a kind of gateway, is very different to the grand, imposing churches and cathedrals of Christianity.
The majority of shrines are not found in the mountains or in the middle of the fields, therefore, but at the borders of mountain villages – which is to say, at what is seen as the edge of the mountains. The tori gate, marking the entrance to a shrine, indicates that there are gods on the other side of it.
Software's girth has surpassed its functionality, largely because hardware advances make this possible. The way to streamline software lies in disciplined methodologies and a return to the essentials.
A primary cause of complexity is that software vendors uncritically adopt almost any feature that users want. Any incompatibility with the original system concept is either ignored or passes unrecognized, which renders the design more complicated and its use more cumbersome. When a system's power is measured by the number of its features, quantity becomes more important than quality. Every new release must offer additional features, even if some don't add functionality.
Customers have trouble distinguishing between essential features and those that are just "nice to have." Examples of the latter class: those arbitrarily overlapping windows suggested by the uncritically but widely adopted desktop metaphor; and fancy icons decorating the screen display, such as antique mailboxes and garbage cans that are further enhanced by the visible movement of selected items toward their ultimate destination. These details are cute but not essential, and they have a hidden cost.
/
Increased complexity results in large part from our recent penchant for friendly user interaction. I've already mentioned windows and icons; color, gray-scales, shadows, pop-ups, pictures, and all kinds of gadgets can easily be added.
A customer who pays—in advance—for service contracts is a more stable income source than a customer who has fully mastered a product's use.
Customer dependence is more profitable than customer education.
What I find truly baffling are manuals—hundreds of pages long—that accompany software applications, programming languages, and operating systems. Unmistakably, they signal both a contorted design that lacks clear concepts and an intent to hook customers.
Initial designs for sophisticated software applications are invariably complicated, even when developed by competent engineers. Truly good solutions emerge after iterative improvements or after redesigns that exploit new insights, and the most rewarding iterations are those that result in program simplifications.
Evolutions of this kind, however, are extremely rare in current software practice—they require time-consuming thought processes that are rarely rewarded. Instead, software inadequacies are typically corrected by quickly conceived additions that invariably result in the well-known bulk.
Time pressure is probably the foremost reason behind the emergence of bulky software. The time pressure that designers endure discourages careful planning. It also discourages improving acceptable solutions; instead, it encourages quickly conceived software additions and corrections. Time pressure gradually corrupts an engineer's standard of quality and perfection. It has a detrimental effect on people as well as products.