hierarchy
Excursus: Homage to the Square^3
The problem with trees
Many systems are organized hierarchically. The CERNDOC documentation system is an example, as is the Unix file system, and the VMS/HELP system. A tree has the practical advantage of giving every node a unique name. However, it does not allow the system to model the real world. For example, in a hierarchical HELP system such as VMS/HELP, one often gets to a lead on a tree such as:
HELP COMPILER SOURCE_FORMAT PRAGMAS DEFAULTS
only to find a reference to another leaf: Please see
HELP COMPILER COMMAND OPTIONS DEFAULTS PRAGMAS
and it is necessary to leave the system and re-enter it. What was needed was a link from one node to another, because in this case the information was not naturally organized into a tree.
The brilliance of notion
This, I think, is the brilliance of Notion, and what makes it one of the best examples of “fidelity to digital information” that I’ve come across. The structure of the app reflects the structure of the web itself: digital content is purposefully formatted, like semantic HTML elements, and exists in a hierarchical structure (directories on the web, nested pages in Notion), yet can be linked and referenced to create a complex network of information. And pages in Notion reveal the structure of the information: when nesting a page within a page, the child page always displays on the parent page. There’s no way to create a child page that doesn’t display on a parent page, no way to obscure the structure of the information. The semantic structure of Notion reflects the semantic structure of the web itself.
Separation and connection in all things
Truchet's approach was more topological than geometric, and the qualitative aspects of pattern take priority over the metric ones. His principles provide a kind of metaphor for the hierarchy of separation and connection in all things.
Ruins, Rub-outs, and Trash
Tracing paper into palimpsest
Kahn's preferred medium was charcoal. He liked to use the side of his hand to rub out the thing he was drawing in order to draw it over, and over again.
Turning the tracing paper into a palimpsest; where some trace of each previous marking is still there, only blurred out and faded back by Kahn's rubbings-out and re-renderings, so that in what he made there is also the record of how it was made.
Charcoal on trash collected over time acting as ersatz animated film recording how Kahn's ideas developed.
So insufficiently palimpsestic
I worry that unlike Kahn's process and tools, the processes and tools we use are aimed at helping us satisfy the demand for moving fast and breaking things, not to be good, or to better ensure the doing of good work.
My son Gerrit told me about a YouTube video from a conference where the presenter asked for a show of hands from video game developers in the audience who could produce or successfully compile their own code from the previous quarter. Or from the previous year. Or from two years ago. And by that time the point had been made: nobody had their hand in the air.
Good for the next man
Lou Kahn said that a house is only good if it's good for "the next man."
He knew that the likelihood of its spaces and places continuing to be loved after "the first man" has come and gone requires the kinds of attention to detail you'd have to be paying if the next man and the next-next man were embraced as stakeholders from the onset.