wabi-sabi
The most incidental detail
Bells
Most Japanese bells when hung still have on them one or more rough lines obviously arising in horizontal mold joints. These lines are not removed in fettling the bell, and they seem to be regarded not as defects but rather as a reminder of the reality of the founder’s interaction with his materials. One is reminded of the ceramics that are most treasured in Japan which usually have some unexpected tool marks or irregularity resulting from a kiln mishap.
Roughness
Roughness is the odd shape, the quick brush stroke, the irregular column size or spacing, the change in pattern at the corner – it is adjusting to conditions as they present themselves with meaning, but without ego or contrived deliberation.
Though it may look superficially flawed, especially with human perception accustomed to mass-produced regularity and perfection as a goal, an object with roughness is often more precise because it comes about from paying attention to what matters most, and letting go of what matters less.
Wabi-sabi
Sabi is an aesthetic term, rooted in a given concern. It is concerned with chronology, with time and its effects, with product.
Wabi is a more philosophical concept, a quality not attached merely to a given object. It is concerned with manner, with process, with direction.
Optical Glass House
A Building by Hiroshi NakamuraA façade of some 6,000 pure-glass blocks (50mm x 235mm x 50mm) was employed. The pure-glass blocks, with their large mass-per-unit area, effectively shut out sound and enable the creation of an open, clearly articulated garden that admits the city scenery. To realize such a façade, glass casting was employed to produce glass of extremely high transparency from borosilicate, the raw material for optical glass. The casting process was exceedingly difficult, for it required both slow cooling to remove residual stress from within the glass, and high dimensional accuracy. Even then, however, the glass retained micro-level surface asperities, but we actively welcomed this effect, for it would produce unexpected optical illusions in the interior space.
How the light gets in
A Quote by Leonard CohenThere is a crack in everything.
That's how the light gets in.Is perfection boring?
An Article by Ralph AmmerWe love to see the process, not just the result. The imperfections in your work can be beautiful if they show your struggle for perfection, not a lack of care.
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.