barnsworthburning.net
- What this site is
- Colophon
- Contact me
- Shortlist of interesting spaces
- Behind the scenes
Your Brain, Your Notes: A clean and powerful notes app for Mac & Windows.
Directories aren’t surging. There isn’t this nascent directory movement fomenting - ready to take on the world. Directories aren’t trending.
But there is a certainly really sweet little directory community now. From the Marijn-inspired stuff listed in Directory Uprising to the link-sharing ‘yesterweb’ collected around sadgrl.online - or the originals at Indieseek and i.webthings.
Barnsworthburning (by Nick Trombley) is a very formidable addition to this community - a clean, multilayered design and an innovative bidirectional index.
One of the best (and easiest) ways to start making sense of a document is to highlight its “important” words, or the words that appear within that document more often than chance would predict. That’s the idea behind Amazon.com’s “Statistically Improbable Phrases”:
Amazon.com’s Statistically Improbable Phrases, or “SIPs”, are the most distinctive phrases in the text of books in the Search Inside!™ program. To identify SIPs, our computers scan the text of all books in the Search Inside! program. If they find a phrase that occurs a large number of times in a particular book relative to all Search Inside! books, that phrase is a SIP in that book.
Highlighter is a personal knowledge bank and collaborative learning network designed to feed your curiosity and help you examine new ideas.
Build ideas mindfully.
Save content, create collections, and connect ideas with other people.
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.
Technology is seeing a little return to complexity. Dreamweaver gave way to hand-coding websites, which is now leading into Webflow, which is a lot like Dreamweaver. Evernote give way to minimal Markdown notes, which are now becoming Notion, Coda, or Craft. Visual Studio was “disrupted” by Sublime Text and TextMate, which are now getting replaced by Visual Studio Code. JIRA was replaced by GitHub issues, which is getting outmoded by Linear. The pendulum swings back and forth, which isn’t a bad thing
A meta note, inspired both by Proust and by this book about Proust: after reading a book, when you're making notes, don't refer to the book; just write down the most interesting things that come to mind. This is a better way of digging out what actually struck you about the book; as soon as you have the book to reference, you will start looking up the bits you "should" write about, and end up aiming at comprehensiveness rather than interestingness. Your actual criterion should be whatever interested you. Later, you can fill in quotations & references.
The visual workspace for notes. Humans have incredible visual-spatial memory. Leverage that with Nototo.
- Pause at the end of each chapter and try to recall it (Recall)
- Highlight relevant passages for later comparative reading
- Analyze the book once I’m finished
- Explain it to unfamiliar audiences (The Feynman technique)
- Review topics I care about at regular intervals (Space repetition)
A note-taking tool for networked thought.
A zettelkasten consists of many individual notes with ideas and other short pieces of information that are taken down as they occur or are acquired. The notes are numbered hierarchically, so that new notes may be inserted at the appropriate place, and contain metadata to allow the note-taker to associate notes with each other. For example, notes may contain tags that describe key aspects of the note, and they may reference other notes. The numbering, metadata, format and structure of the notes is subject to variation depending on the specific method employed.
Evergreen notes are written and organized to evolve, contribute, and accumulate over time, across projects. This is an unusual way to think about writing notes: Most people take only transient notes.
- Evergreen notes should be atomic
- Evergreen notes should be concept-oriented
- Evergreen notes should be densely linked
- Prefer associative ontologies to hierarchical taxonomies
The problems are solved, not by giving new information, but by arranging what we have known since long.
Intelligent note-taking. Non-linear file management. Ideas and relationships visualized.
In order that the mind may not be taxed, moreover, by the manifold and confused reading of so many such things, and in order to prevent the escape of something valuable that we have read, heard, or discovered through the process of thinking itself, it will be found very useful to entrust to notebooks...those things which seem noteworthy and striking.
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.
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.
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.
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.
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.
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.