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
Product vs. Feature Teams An Article by Marty Cagan svpg.com This article is certain to upset many people. Empowered product teamsViability, usablity, feasibilityWhat went wrong? featuressoftwareagile
Empowered product teams When I wrote about the virtues of empowered product teams, I was referring to what I’ll continue to call here as product teams. Specifically, they are cross-functional (product, design and engineering); they are focused on and measured by outcomes (rather than output); and they are empowered to figure out the best way to solve the problems they’ve been asked to solve.
Viability, usablity, feasibility In an empowered product team, the product manager is explicitly responsible for ensuring value and viability; the designer is responsible for ensuring usability; and the tech lead is responsible for ensuring feasibility. The team does this by truly collaborating in an intense, give and take, in order to discover a solution that work for all of us. However, in a feature team, you still (hopefully) have a designer to ensure usability, and you have engineers to ensure feasibility, but, and this is critical to understand: the value and business viability are the responsibility of the stakeholder or executive that requested the feature on the roadmap. What went wrong? teamwork
What went wrong? If something ships from one of the companies I advise, and it is virtually unusable because of poor design (which as we all know occasionally does happen), you can bet I go directly to the designer and ask how this happened? It is absolutely on the designer to ensure this does not happen, so something went wrong. Similarly, if the product ships and performance is terrible you can bet I go directly to the tech lead with the same question. And most frequently of all, if something ships and the analytics show that it’s either not being bought or not being used, or it turns out that it violates some business constraint like compliance or privacy, you can bet I go right to the product manager with that question. Viability, usablity, feasibility