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
Manifesto for Agile Software Development A Definition agilemanifesto.org We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. Deliver early and continuouslyWelcome changing requirementsSelf-organizing teamsTechnical excellence and good designAgility and sustainability+7 More agileprocesssoftware
Deliver early and continuously Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Welcome changing requirements Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. A late change in requirements is a competitive advantage planning
Self-organizing teams The best architectures, requirements, and designs emerge from self-organizing teams.
Technical excellence and good design Continuous attention to technical excellence and good design enhances agility. craft
Agility and sustainability Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
The amount of work not done Simplicity—the art of maximizing the amount of work not done—is essential. -2000 Lines Of Code simplicity
Build projects around motivated individuals Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. On ValueOn Talent
Deliver working software frequently Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Business people and developers Business people and developers must work together daily throughout the project. collaboration
Face-to-face conversations The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. teamwork
Reflect, tune, adjust At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.