It is unusual to find such mismatched elements on a single facade as this fine stonework coexisting with these stained and rotting shutters, on a house in the fortified town of Feltre, in the northern Italian province of Belluno.
Where considerable labour lies behind the cutting and fitting of the stone, the timber planks have been left in their raw state, with no paint or carved decoration. Even the iron hinges are of the plainest variety.
We should note that all of these places of thermal extremes (Finnish saunas, Japanese hot baths, American beaches and mountains) have their opposites close at hand. There are possibly two reasons for having the extremes right next to each other.
The first is physiological: the availability of extremes ensures that we can move from one to the other to maintain a thermal balance.
The second might be termed aesthetic: the experience of each extreme is made more acute by contrast to the other.
Works of art which have great life often have intense contrast within: rough/smooth, solid/void, loud/silent, empty/full. It is the difference between opposites which gives birth to something. Contrast is what often gives other principles their degree of life – the intensity of the boundary, the markedness of the alternating repetition.
Contrast strengthens centers by making each a deeper entity of itself, and thereby giving deeper meaning to both. It is, at its simplest, what allows us to differentiate. But meaningless contrast remains meaningless. It is only when centers are actively, mutually, and meaningfully composed that it acts to deepen the whole.
While the client has some knowledge of his symptoms, he may not understand the real causes of them, and it is foolish to try to cure the symptoms only. Thus while the systems engineers must listen to the client, they should also try to extract from the client a deeper understanding of the phenomena. Therefore, part of the job of a systems engineer is to define, in a deeper sense, what the problem is and to pass from the symptoms to the causes.
Just as there is no definite system within which the solution is to be found, and the boundaries of the problem are elastic and tend to expand with each round of solution, so too there is often no final solution, yet each cycle of input and solution is worth the effort. A solution which does not prepare for the next round with some increased insight is hardly a solution at all.
I suppose the heart of systems engineering is the acceptance that there is neither a definite fixed problem nor a final solution, rather evolution is the natural state of affairs. This is, of course, not what you learn in school, where you are given definite problems which have definite solutions.