We simply can no longer design and develop only for “optimal” content or browsing conditions. Instead, we must embrace the inherent flexibility and unpredictability of the web, and build resilient components. Static mockups cannot cater to every scenario, so many design decisions fall to developers at build time. Like it or not, if you’re a UI developer, you are a designer — even if you don’t consider yourself one!
...Sometimes interpreting a design means asking the designer to further elaborate on their ideas (or even re-evaluate them). Other times, it means making design decisions on the fly or making recommendations based on our knowledge and experience.
There is a story of Rikyu which well illustrates the ideas of cleanliness entertained by the tea masters. Rikyu was watching his son Shoan as he swept and watered the garden path. "Not clean enough," said Rikyu, when Shoan had finished his task, and bade him try again. After a weary hour the son turned to Rikyu: "Father, there is nothing more to be done. The steps have been washed for the third time, the stone lanterns and the trees are well sprinkled with water, moss and lichens are shining with a fresh verdure; not a twig, not a leaf have I left on the ground"
"Young fool," chided the tea master, "that is not the way a garden path should be swept. "Saying this, Rikyu stepped into the garden, shook a tree and scattered over the garden gold and crimson leaves, scraps of the brocade of autumn! What Rikvu demanded was not cleanliness alone, but the beautiful and the natural also.