A time when time was not Darkness cannot say: “I precede the coming light”, but there is a sense in which light can say, “Darkness preceded me”. Doubtless there is an event, X, in the future, by reference to which we may say that we are at present in a category of Not-X, but until X occurs, the category of Not-X is without reality. Only X can give reality to Not-X; that is to say, Not-Being depends for its reality upon Being. In this way we may faintly see how the creation of Time may be said automatically to create a time when Time was not, and how the Being of God can be said to create a Not-Being that is not God. Dorothy Sayers, The Mind of the Maker darknesslighttimebeing
Thin ice Today the 'depth of our being' stands on thin ice. Juhani Pallasmaa, The Eyes of the Skin: Architecture and the Senses coldbeing
The utter nothingness of being Everything written symbols can say has already passed by. They are like tracks left by animals. That is why the masters of meditation refuse to accept that writings are final. The aim is to reach true being by means of those tracks, those letters, those signs - but reality itself is not a sign, and it leaves no tracks. It doesn’t come to us by way of letters or words. We can go toward it, by following those words and letters back to what they came from. But so long as we are preoccupied with symbols, theories and opinions, we will fail to reach the principle. "But when we give up symbols and opinions, aren’t we left in the utter nothingness of being?" Yes. Kimura Kyūho, On the Mysteries of Swordsmanship The Elements of Typographic Style zenmeaningsymbolsbeingreality
What will be has always been A Quote by Louis Kahn understandinggroup.com Ruins, Rub-outs, and Trash timebeing
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