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
Figma's Engineering Values: Craftsmanship An Article www.figma.com Craftsmanship is about thoughtfulness and care in the work we do. It means being deliberate about what we build and how possible it will be to maintain and extend in the future. A solution that will require revisiting in a month — because it’s not scaling, because it has a ton of bugs, because it doesn’t support all the use cases it needs to — is not useful to us and ultimately will generate pain for our users. What we trade off by living this value is (sometimes) day-to-day speed. It’s easy to imagine an engineering team that emphasizes moving fast over keeping things stable and bug-free -- like a team building a product that isn’t responsible for important user data and doesn’t support anyone’s livelihood. But given the role the Figma product plays in the lives of our users, we feel it’s worth it to ensure we hold a high quality bar for them. And in the long run, being thoughtful about how we build often reduces the complexity of ongoing development and new features regardless. craftsoftwarequality