water
Watermill
Rain Chains & Musical Drains
A rain chain in winter; Dresden Kunsthof Passage; Drainage planters near Pike Place Market in Seattle.
If there is a larger takeaway here perhaps it is about paths of least resistance, with regards to both the actual flow of water and design decisions. On the one hand, it is easy to blindly follow regional precedents and traditions with long histories (or grab whatever is handy at the hardware store). On the other hand, sometimes it makes sense to take a step back and decide consciously how to reveal (or conceal) a natural process.
The Beauty of the Overlooked
An Article by Maria PopovaMedusa from A Naturalist’s Rambles on the Devonshire Coast by Philip Henry Gosse, 1853.
Philip Henry Gosse’s Stunning 19th-Century Illustrations of Coastal Creatures and Reflections on the Delicate Kinship of Life
“These objects are, it is true, among the humblest of creatures that are endowed with organic life… Here we catch the first kindling of that spark, which glows into so noble a flame in the Aristotles, the Newtons, and the Miltons of our heaven-gazing race.”
Rain chains
An ObjectRain chains are a beautiful and functional alternative to traditional, closed gutter downspouts. Guiding rain water visibly down chains or cups from the roof to the ground, rain chains transform a plain gutter downspout into a pleasing water feature. From the soft tinkling of individual droplets to the soothing rush of white water, they are a treat to listen to.
Rain chains (‘kusari doi’ in Japanese) in concept are not a new idea. For hundreds of years, the Japanese have used the roof of their homes to collect water, transporting it downward with chains and finally depositing the rain water into large barrels for household water usage. Japanese temples often incorporate quite ornate and large rain chains into their design.
On the "Building" of Software and Websites
I’m beginning to suspect that software, and more conspicuously the Web, is fundamentally the wrong shape for the archetype of the construction project.
You are agreeing to make a Thing
When you sign the contract for the construction project, you are agreeing to make a Thing—app, website, whatever. And you will have agreed to deliver this Thing on a certain date, also known as a deadline. From this point forward, the goals of shipping the Thing on time and actually solving the client’s problem will be in competition with each other.
The Thing-deadline calculus
Now, I understand deadlines. I understand that the plane will take off whether or not I’m on it, or the importance of beating the holiday retail rush, or that "the show must go on". It is perfectly clear to me how people use timekeeping technology to coordinate social activity. It’s actually quite remarkable when you step back and look at it. But, over the years, I have observed that there is a difference between those examples and the ones around the delivery of Things, which tend to be completely arbitrary. When you wrap an arbitrarily complex endeavor up in a neat launch date, the goal seems to be more about coercing the people beneath you to absorb the overhead of all the details you left out—that or sweating it yourself. As a tool for coordinating human activity, I have come to believe that the Thing-deadline calculus is, considering more sophisticated alternatives, unnecessarily crude.
Trees and graphs
A tree is a kind of graph, but a graph can be considerably more complex than a tree.
I have reason to believe, which for brevity’s sake I will treat elsewhere, that the most complex class of processes and structures we humans can consciously prescribe, reduces mathematically to a tree. A tree has a top, bottom, left and right. Its branches fan out from the trunk and they don’t intersect with one another. They are discrete, contiguous, identifiable objects which persist across time. Trees are Things.
Software and websites, however, reduce to arbitrarily more complex structures: they are graphs. A graph has no meaningful orientation whatsoever. No sequence, no obvious start or end—at least none that we can intuit. It is better considered not as one Thing, but as a federation of Things, like the brain or a fungus network, or perhaps a composite artifact left behind from an ongoing process, like an ant colony or human city.
Content as value
The most important consideration for any software or web excursion is content: the content of the text and other communicative media, as well as the content of the code that executes the business processes. The ability to tick off a page or piece of functionality as being done only produces a nominal successful result; the careful crafting of what one of these objects says produces a real one.