Church on the Water, Hokkaido, 1985–8 At the edges of the outer walls to left and right, the slate floor is held back, creating a shadowed slot into which the concrete wall slips out of sight. Because the wall does not meet and bear upon the floor, as is usual, the relationship of the wall to the ground is uncertain, and the rippling surface of the black slate floor appears to float free of the walls, merging with the rippling surface of the water. Robert McCarter & Juhani Pallasmaa, Understanding Architecture weight
Lightness & Heaviness "Lightness is born of heaviness and heaviness of lightness, instantaneously and reciprocally, returning creation for creation, gaining strength proportionally as they gain in life, and as much more in life as they gain in motion. They destroy one another also at the same time, fulfilling a mutual vendetta, proof that lightness is created only in conjunction with heaviness, and heaviness only where lightness follows." — Leonardo da Vinci Robert McCarter & Juhani Pallasmaa, Understanding Architecture materialweight
Buttresses Buttresses, Ruskin writes, are structures against pressure: a cathedral’s walls want to fall outward, for example, pushed aside by the relentless weight of the roof. But this gravitational pressure can be stabilized by an exoskeleton: a sequence of buttresses that will prevent those walls from collapsing outward. However, Ruskin points out, there is a similar kind of pressure from the waves of the sea. Think of the curved hull of a ship, he writes, which is internally buttressed against the “crushing force” of the ocean around it. It is a kind of inside-out cathedral. Geoff Manaugh, BLDGBLOG www.bldgblog.com weightarchitecture
The heart of systems engineering 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. Richard Hamming, The Art of Doing Science and Engineering: Learning to Learn What the problem isComplete and consistent requirements