Only in terms of other things No legislation could prevent the making of verbal pictures: God walks in the garden, He stretches out His arm, His voice shakes the cedars, His eyelids try the children of men. To forbid the making of pictures about God would be to forbid thinking about God at all, for man is so made that he has no way to think except in pictures. But continually, throughout the history of the Jewish-Christian Church, the voice of warning has been raised against the power of the picture-makers: “God is a spirit”, “without body, parts or passions”; He is pure being, “I AM THAT I AM”. The fact is, that all language about everything is analogical; we think in a series of metaphors. We can explain nothing in terms of itself, but only in terms of other things. Dorothy Sayers, The Mind of the Maker Metaphors We Live ByYou only understand something relative to something you already understand metaphoranalogy
The strange familiar and the familiar strange The problem solver, when confronted with a new and yet unsolved problem, overlays the structure of the unsolved problem with an apparently similar problem with which he or she is experienced. Making the strange familiar and the familiar strange are also principally based on the use of analogy. Peter G. Rowe, Design Thinking metaphoranalogy
One Tenth of a Second An Article by Venkatesh Rao studio.ribbonfarm.com The details are fascinating, but the central argument — that the birth of modernity can be traced to a meta-crisis spawned by the 0.1s problem — is worth understanding and appreciating whether or not you’re a time nerd like me. There is no convenient leitmotif, comparable to the 0.1s problem, for our contemporary version of the rhyming conditions, but something very similar to the “tenth of a second crisis” is going on today. I suspect our Great Weirding too involves some sort of limiting factor on human cognition that we haven’t yet properly wrapped our minds around. It isn’t reaction time, but something analogous. timeanalogyprogresscognition
The heart of systems engineering While the client has some knowledge of his symptoms, he may not understand the real causes of them, and it is foolish to try to cure the symptoms only. Thus while the systems engineers must listen to the client, they should also try to extract from the client a deeper understanding of the phenomena. Therefore, part of the job of a systems engineer is to define, in a deeper sense, what the problem is and to pass from the symptoms to the causes. Just as there is no definite system within which the solution is to be found, and the boundaries of the problem are elastic and tend to expand with each round of solution, so too there is often no final solution, yet each cycle of input and solution is worth the effort. A solution which does not prepare for the next round with some increased insight is hardly a solution at all. I suppose the heart of systems engineering is the acceptance that there is neither a definite fixed problem nor a final solution, rather evolution is the natural state of affairs. This is, of course, not what you learn in school, where you are given definite problems which have definite solutions. Richard Hamming, The Art of Doing Science and Engineering: Learning to Learn What the problem isComplete and consistent requirements