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.
On Motivation
I’ve had this (semi-vague) idea that I want to write about what keeps us excited to work on Are.na, on the occasion of its 10th (yes 10th) birthday. While writing generally is a tricky process for me, this subject motivation is even trickier.
In turning this subject around in my mind, and thinking about all the people and things that have been influential, I have some idea about what keeps us going.
Nodal points
I started thinking about all the other important “nodal points” (I don’t know what else to call this) of people, places, books, albums, websites, etc. that all played a part in shaping who I am as a person and what I think is important. These points are a combination of seeking things out myself and getting a recommendation that felt like it was actually for me. A mixture of both passive and active knowledge acquisition.
ultimately, it's the totality of those “nodal points” that indicate one’s own unique perspective. It doesn’t matter if you specifically sought out the nodal point or not, it’s the recognition that counts. When you encounter a piece of life-changing information (no matter how large the change part is), you are simultaneously discovering and creating “yourself,” becoming incrementally more complete. Your perspective (where your gaze is directed) is made up of a meandering line through these points. Learning (or maybe some precursor to learning) is a lot about developing the intuition to recognize when something you find in the world is going to be a nodal point for you.
Infinite varieties of contexts
Over the course of 10 years of using Are.na, I have fully adopted the view that any piece of information can be important to a person given the right context. And on Are.na, pieces of information can be arranged in infinite varieties of contexts – their respective meaning shifts as the proximate information shifts. In other words, the more connections a block has, the more opportunities it has to be a nodal point.
A lifelong project
One question that is still hard to answer after 10 years of working on Are.na is “what is the long term vision?” This is difficult for a few reasons.
One reason is that we have to calibrate our definition of long term with the person who is asking the question. Are.na is a lifelong project. Our ideal outcome as a company is not becoming the next Facebook (god forbid), it’s becoming the next Nishiyama Onsen Keiunkan, a hot spring hotel in Japan, and one of the world’s oldest businesses (founded in 705 AD).
Growing in the correct way
It often feels like Are.na itself has its own needs and desires—that Are.na has its own personal intuition. And that we (you and I) are figuring out what it wants to be together. We (the organization that works on Are.na) have a very defined sense of how things should be done and why building Are.na is important, but we try not to be overly dogmatic about what exactly it should evolve into.
…We’ve long had the sense that it’s possible to cultivate an experience on the Internet that is more calm, thoughtful, and introspective. And we’ve long had the view that this is possible not from a technology-oriented approach, but from an approach that is more soft, more personal, and more intuitive.
…If we are the blade, what is the shield? I think it’s speed: The dominant model for online platforms (especially social platforms) is speed and scale at all costs. But to us, growing Are.na in the correct way is more important than growing it quickly.