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
Problems With Agile UX A Podcast by Laura Klein & Kate Rutter www.usersknow.com So that you can get feedback on it and make it betterI'm sorry, I love engineers
So that you can get feedback on it and make it better Fascinatingly, one of the other big complaints people had about agile is no iteration. I don't understand how being in an agile environment makes people less iterative, but somehow that seems to be the case. And I think it's because people misunderstand and think that agile is just about putting features out faster, and not about the important part, which is getting something in front of users faster so that you can get feedback on it and make it better. The most rewarding iterationsTo anticipate all the uses and abuses agileiteration
I'm sorry, I love engineers People are afraid to let design have time to actually figure out the right thing to make, because "whatever will the engineers do?" – fuck you, there's plenty for the engineers to do. Go fix some technical debt. Go fix those 700 bugs that you de-prioritized or marked as won't fix because you're an asshole. I'm sorry, I love engineers. I don't know why I'm yelling at them. But you know, there's plenty for the engineers to do. There's all sorts of cleanup. They can work on dev-ops stuff! They can work on their build process! Make it faster! I'm not worried about keeping the engineers busy. If you think that the only thing that engineers can do is build yet another stupid feature that nobody is going to use, then you're a garbage designer and you should quit. ...Happy 2020 everybody! engineeringuxfeaturesrepair