spirit
Ordinariness
Flight of the soot sprites
The ancient fire spirit who lived in the hearth
The garden is as central to the concept of an Islamic home as the hearth is to the European home. It is interesting, then, that the hearth-fire in old traditions has a similar association with the life of the inhabitants of the house.
Commonly, the fire of the hearth was not allowed to go out. It was carefully covered with ashes each night at curfew so that a few selected embers would survive until morning. (In fact, the word "curfew" originated from the French word for cover-the-fire—couvre-feu.) Raglan comments that "the alarm and horror felt if the hearth-fire went out are out of all proportion to the inconvenience caused" by the need to relight it.
Retained as a quality
Thermal information is not differentiated in our memory; rather it is retained as a quality, or underlying tone, associated with the whole experience of the place. It contributes to our sense of the particular personality, or spirit, that we identify with that place. In remembering the spirit of a place, we can anticipate that if we return, we will have the same sense of comfort or relaxation as before.
Roaming and capricious
Now I sometimes wonder whether the current of utility has not become too strong and whether there would be sufficient opportunity for a full life if the world were emptied of some of the useless things that give it spiritual significance; in other words, whether our conception of what is useful may not have become too narrow to be adequate to the roaming and capricious possibilities of the human spirit.
My Neighbor Totoro
A Film by Hayao MiyazakiSpirited Away
A Film by Hayao MiyazakiAvatar: The Last Airbender
A SeriesThe Legend of Korra
A Series
A Plea for Lean Software
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.
Measured by the number of its features
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.
Essential vs. nice to have
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.
Dependence is more profitable than education
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.
The most rewarding iterations
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.
Never enough time
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.