Tell me, gentle flowers Tell me, gentle flowers, teardrops of the stars, standing in the garden, nodding your heads to the bees as they sing of the dews and the sunbeams, are you aware of the fearful doom that awaits vou? Dream on, sway and frolic while you may in the gentle breezes of summer. Tomorrow a ruthless hand will close around your throats. Okakura Kakuzō, The Book of Tea flowers
The man of the pot In the West the display of flowers seems to be a part of the pageantry of wealth—the fancy of a moment. Whither do they all go, these flowers, when the revelry is over? Nothing is more pitiful than to see a faded flower remorselessly flung upon a dung heap. ...Much may be said in favor of him who cultivates plants. The man of the pot is far more humane than he of the scissors. ...Anyone acquainted with the ways of our tea and Flower Masters must have noticed the religious veneration with which they regard flowers. They do not cull at random, but carefully select each branch or spray with an eye to the artistic composition they have in mind. They would be ashamed should they chance to cut more than were absolutely necessary. It may be remarked in this connection that they always associate the leaves, if there be any, with the flower, for their object is to present the whole beauty of plant life. In this respect, as in many others, their method differs from that pursued in Western countries. Here we are apt to see only the flower stems, heads as it were, without body, stuck promiscuously into a vase. Okakura Kakuzō, The Book of Tea flowersgardens
If removed from the place for which it was intended A flower arrangement by a tea master loses its significance if removed from the place for which it was originally intended, for its lines and proportions have been specially worked out with a view to its surroundings. Okakura Kakuzō, The Book of Tea Conditional art flowers
Feature parity An Article martinfowler.com Whilst Feature Parity often sounds like a reasonable proposition, we have learnt the hard way that people greatly underestimate the effort required, and thus misjudge the choice between this and the other alternatives. For example even just defining the 'as is' scope can be a huge effort, especially for legacy systems that have become core to the business. Most legacy systems have 'bloated' over time, with many features unused by users (50% according to a 2014 Standish Group report) as new features have been added without the old ones being removed. Workarounds for past bugs and limitations have become 'must have' requirements for current business processes, with the way users work defined as much by the limitations of legacy as anything else. Rebuilding these features is not only waste it also represents a missed opportunity to build what is actually needed today. These systems were often defined 10 or 20 years ago within the constraints of previous generations of technology, it very rarely makes sense to replicate them 'as is'. softwarefeaturesrepair