As George Lakoff and Mark Johnson made clear in their touchstone book Metaphors We Live By, metaphors are the basis of all human thought and reasoning. The metaphors we use to speak about the web are not simply linguistic trivia – they determine how we understand it on a fundamental level. It determines what we think the web is capable of, what risks, opportunities, and challenges it poses. Which means the metaphors we use to think about the web profoundly influence what we think the web is, what we think we can do with it, and how we might change or evolve it.
…Out of all of these metaphors [for the web], the two most enduring are paper and physical space.
Digital gardening is the Domestic Cozy version of the personal blog. It's less performative than a blog, but more intentional and thoughtful than our Twitter feed. It wants to build personal knowledge over time, rather than engage in banter and quippy conversations.
An open collection of notes, resources, sketches, and explorations I'm currently cultivating. Some notes are Seedlings, some are budding, and some are fully grown Evergreen.
Who advocates in the requirements process for the product itself—its conceptual integrity, its efficiency, its economy, it’s robustness? Often, no one. As often, an architect or engineer who can offer only opinion based on taste and instinct, unbuttressed as yet by facts. For in a classical Waterfall Model product process, requirements are set before design is begun.
The result, of course, is a grossly obese set of requirements, the union of many wish lists, assembled without constraints. Usually, the list is neither prioritized nor weighted. The social forces in the committee forbid the painful conflicts occasioned by even weighting, much less prioritizing.