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.
On the "Building" of Software and Websites
I’m beginning to suspect that software, and more conspicuously the Web, is fundamentally the wrong shape for the archetype of the construction project.
You are agreeing to make a Thing
When you sign the contract for the construction project, you are agreeing to make a Thing—app, website, whatever. And you will have agreed to deliver this Thing on a certain date, also known as a deadline. From this point forward, the goals of shipping the Thing on time and actually solving the client’s problem will be in competition with each other.
The Thing-deadline calculus
Now, I understand deadlines. I understand that the plane will take off whether or not I’m on it, or the importance of beating the holiday retail rush, or that "the show must go on". It is perfectly clear to me how people use timekeeping technology to coordinate social activity. It’s actually quite remarkable when you step back and look at it. But, over the years, I have observed that there is a difference between those examples and the ones around the delivery of Things, which tend to be completely arbitrary. When you wrap an arbitrarily complex endeavor up in a neat launch date, the goal seems to be more about coercing the people beneath you to absorb the overhead of all the details you left out—that or sweating it yourself. As a tool for coordinating human activity, I have come to believe that the Thing-deadline calculus is, considering more sophisticated alternatives, unnecessarily crude.
Trees and graphs
A tree is a kind of graph, but a graph can be considerably more complex than a tree.
I have reason to believe, which for brevity’s sake I will treat elsewhere, that the most complex class of processes and structures we humans can consciously prescribe, reduces mathematically to a tree. A tree has a top, bottom, left and right. Its branches fan out from the trunk and they don’t intersect with one another. They are discrete, contiguous, identifiable objects which persist across time. Trees are Things.
Software and websites, however, reduce to arbitrarily more complex structures: they are graphs. A graph has no meaningful orientation whatsoever. No sequence, no obvious start or end—at least none that we can intuit. It is better considered not as one Thing, but as a federation of Things, like the brain or a fungus network, or perhaps a composite artifact left behind from an ongoing process, like an ant colony or human city.
Content as value
The most important consideration for any software or web excursion is content: the content of the text and other communicative media, as well as the content of the code that executes the business processes. The ability to tick off a page or piece of functionality as being done only produces a nominal successful result; the careful crafting of what one of these objects says produces a real one.