networks
A representational tension
The number of ways in which things work
Trees and graphs
Information remix
Effective writing stems from intelligently connecting the dots between the concepts you understand and can articulate. It stands to reason, then, that in order to generate more creativity you must not only add to a knowledge base, but deepen and expand the number of connections within the totality of the network. By establishing and explicitly mapping your knowledge, you allow yourself the freedom to remix information. You will often find that solutions come from previously unsuspected fields or topics—proving to be analogous in some shape or form.
The network of connections
Each pattern depends both on the smaller patterns it contains, and on the larger patterns within which is is contained. Each pattern sits at the center of a network of connections which connect it to certain other patterns that help to complete it. It is the network of these connections between patterns which creates the language.
Not an accumulation of facts
Knowledge is not an accumulation of facts, nor is it even a set of facts and their relations. Facts are only rendered meaningful within narratives, and the single-page document is a format very conducive to narrative structure. The hypertext books that have gained popularity (I’m thinking here of Meaningness.com) have largely conformed to this in two ways: 1) there is an intended reading order, and 2) the longer essays within the project do most of the heavy lifting in terms of imparting the author’s perspective to readers.
On the other hand, the notion of the “document” that is intrinsic to web development today is overdetermined by the legacy of print media. The web document is a static, finished artifact that does not bring in dynamic data. This is strange because it lives on a medium that is alive, networked, and dynamic, a medium which we increasingly understand more as a space than a thing.
Infrastructure: A Guide to the Industrial Landscape
A Book by Brian HayesInteroperable Personal Libraries and Ad Hoc Reading Groups
An Article by Maggie AppletonWe would need a system that enables people to:
- Publish a list of books they would be willing to discuss with other people to the open web. Antilibraries – collections of books you haven't read yet but would like to read – are particularly well suited to this proposition.
- See which books people in their social network want to discuss, and/or subscribe to other people's lists
- Be notified when 4+ people in their network have the same book on their discussion list – possibly via an email thread?
- Coordinate and schedule a time to read and discuss the book with that group.
Obsidian
An ApplicationObsidian is a powerful knowledge base that works on top of a local folder of plain text Markdown files.
In Obsidian, making and following [[connections]] is frictionless. Tend to your notes like a gardener; at the end of the day, sit back and marvel at your own knowledge graph.
are.na
An Application by Charles BroskoskiBuild ideas mindfully.
Save content, create collections, and connect ideas with other people.
All websites are just digital movie theaters now
An Article by Ryan BroderickIf I had to guess where this is all going, I’d say that what an internet platform is actually has already permanently shifted. Instead of apps trying to dominate specific features — a platform for video, a platform for expiring content, a platform for connecting social networking, a platform for livestreaming, a platform for resumes — we’ve already entered a new era of online networks where they all will essentially offer the same services and instead, focus increasingly on specific demographics.
Roam Research
An ApplicationA note-taking tool for networked thought.
- are.na
InfoCrystal
A Research PaperThis paper introduces a novel representation, called the InfoCrystal, that can be used as a visualization tool as well as a visual query language to help users search for information. The InfoCrystal visualizes all the possible relationships among N concepts.
The Brain
An ApplicationIntelligent note-taking. Non-linear file management. Ideas and relationships visualized.
A Plea for Lean Software
Software's girth has surpassed its functionality, largely because hardware advances make this possible. The way to streamline software lies in disciplined methodologies and a return to the essentials.
Measured by the number of its features
A primary cause of complexity is that software vendors uncritically adopt almost any feature that users want. Any incompatibility with the original system concept is either ignored or passes unrecognized, which renders the design more complicated and its use more cumbersome. When a system's power is measured by the number of its features, quantity becomes more important than quality. Every new release must offer additional features, even if some don't add functionality.
Essential vs. nice to have
Customers have trouble distinguishing between essential features and those that are just "nice to have." Examples of the latter class: those arbitrarily overlapping windows suggested by the uncritically but widely adopted desktop metaphor; and fancy icons decorating the screen display, such as antique mailboxes and garbage cans that are further enhanced by the visible movement of selected items toward their ultimate destination. These details are cute but not essential, and they have a hidden cost.
/
Increased complexity results in large part from our recent penchant for friendly user interaction. I've already mentioned windows and icons; color, gray-scales, shadows, pop-ups, pictures, and all kinds of gadgets can easily be added.
Dependence is more profitable than education
A customer who pays—in advance—for service contracts is a more stable income source than a customer who has fully mastered a product's use.
Customer dependence is more profitable than customer education.
What I find truly baffling are manuals—hundreds of pages long—that accompany software applications, programming languages, and operating systems. Unmistakably, they signal both a contorted design that lacks clear concepts and an intent to hook customers.
The most rewarding iterations
Initial designs for sophisticated software applications are invariably complicated, even when developed by competent engineers. Truly good solutions emerge after iterative improvements or after redesigns that exploit new insights, and the most rewarding iterations are those that result in program simplifications.
Evolutions of this kind, however, are extremely rare in current software practice—they require time-consuming thought processes that are rarely rewarded. Instead, software inadequacies are typically corrected by quickly conceived additions that invariably result in the well-known bulk.
Never enough time
Time pressure is probably the foremost reason behind the emergence of bulky software. The time pressure that designers endure discourages careful planning. It also discourages improving acceptable solutions; instead, it encourages quickly conceived software additions and corrections. Time pressure gradually corrupts an engineer's standard of quality and perfection. It has a detrimental effect on people as well as products.