Yanagi Sōetsu
What is Pattern?
Handicrafts and Sesshu
Okinawa's Bashofu
A Painted Karatsu as Food for Thought
Recently there is a tendency to pursue distortion in art, but in the case of this jar, natural deformation has raised distortion to the level of spontaneous beauty.
Woodblock Prints
An Essay from The Beauty of Everyday Things by Yanagi SōetsuIt seems to me that many printmakers are suffering under a delusion. Looking at current trends, it appears that recent prints are simply copying fine art and painting. Some printmakers are working in the nanga style of painting. Others are attempting to reproduce the effects of oil. Some cleverly contrived prints are often difficult to distinguish from paintings done with a brush. The question arises: Why are these printmakers working in the medium of woodblock printing at all?
For prints to follow in the footsteps of painting has very little meaning. The art of the brush and palette should be left to the brush and palette.
Seeing and Knowing
An Essay from The Beauty of Everyday Things by Yanagi SōetsuThe results of intuition can be studied by the intellect, but the intellect cannot give birth to intuition.
The Japanese Perspective
An Essay from The Beauty of Everyday Things by Yanagi SōetsuGenerally speaking, the Western perception of art has its roots in Greece. For a long time its goal was perfection, which is particularly noticeable in Greek sculpture. This was in keeping with Western scientific thinking; there are no painters like Andrea Mantegna in the East. I am tempted to call such art ‘the art of even numbers’.
In contrast to this, what the Japanese eye sought was the beauty of imperfection, which I would call ‘the art of odd numbers’. No other country has pursued the art of imperfection as eagerly as Japan.
The Beauty of Kasuri
An Essay from The Beauty of Everyday Things by Yanagi SōetsuThe Characteristics of Kogin
An Essay from The Beauty of Everyday Things by Yanagi SōetsuThe Beauty of Miscellaneous Things
An Essay from The Beauty of Everyday Things by Yanagi SōetsuWashi
An Essay from The Beauty of Everyday Things by Yanagi SōetsuHandmade washi (traditional Japanese paper) is replete with appeal. Looking at it, touching it, fills me with an indescribable sense of satisfaction. The more beautiful it is, however, the more difficult it is to put to use. Only a master of calligraphy could possibly add to its beauty; it is exquisite just as it is. This is wonderfully strange, for it is merely a simple material. Yet plain and undecorated as it is, it is alive with nuanced beauty. Good washi makes possible our most ambitious creative dreams.
What is Folk Craft?
An Essay from The Beauty of Everyday Things by Yanagi Sōetsu
The Fidelity Curve
How do we choose which level of fidelity is appropriate for a project?
I think about it like this: The purpose of making sketches and mockups before coding is to gain confidence in what we plan to do. I’m trying to remove risk from the decision to build something by somehow “previewing” it in a cheaper form. There’s a trade-off here. The higher the fidelity of the mockup, the more confidence it gives me. But the longer it takes to create that mockup, the more time I’ve wasted on an intermediate step before building the real thing.
I like to look at that trade-off economically. Each method reduces risk by letting me preview the outcome at lower fidelity, at the cost of time spent on it. The cost/benefit of each type of mockup is going to vary depending on the fidelity of the simulation and the work involved in building the real thing.
Four levels of fidelity
Suppose we have four levels of fidelity…
- Rough sketch (on paper or an iPad)
- Static mock-up (eg. Photoshop or Sketch)
- Interactive mock-up (eg. Framer, InVision)
- Working code prototype (HTML/CSS, iOS views)
Depending on the feature you’re working on, these levels of fidelity take different amounts of time to create. If you plot them in terms of time to build versus confidence gained, you could imagine something like a per-feature fidelity curve.
Time to build versus confidence gained
Take a simple CRUD web UI, where you’re just navigating between screens. It doesn’t take much more time to build the real version than it does to mock it when the design is simple. If you were to build out an interactive mock first, you would end up spending twice as much time in total without gaining much out of it.
Contrast that with a complicated Javascript interaction. Or a native iOS feature that requires programmer time to build out. If it takes substantially more time to build the real code version, then it may be smart to do an interactive mockup first.