Memory
From the head of Jove
Ise Shrines, Nagoya, 685–Present
Amassing the archive
What were you trying to protect?
Retained as a quality
The significance of love's burden
Mental infrastructure
Memory prompts
To serve as a reminder
The bloodless ghosts of memory
Can you even call it memory?
In our bodies
Memory & Fantasy
I can't remember
Refuges
The odor of raisins
To fill in the gaps
Homes at Night
The brag document
An Article by Julia EvansIt’s frustrating to have done something really important and later realize that you didn’t get rewarded for it just because the people making the decision didn’t understand or remember what you did.
The tactic is pretty simple! Instead of trying to remember everything you did with your brain, maintain a “brag document” that lists everything so you can refer to it when you get to performance review season!
The primacy of interpretation over sensation
A Fragment by Mark LibermanOur memory of exact word sequences usually fades more quickly than our memory of (contextually interpreted) meanings.
More broadly, the exact auditory sensations normally fade very quickly; the corresponding word sequences fade a bit more slowly; and the interpreted meanings last longest.
These generalizations can be overcome to some extent if the sound or the text has especially memorable characteristics. (And the question of what "memorable" means in this context is interesting.)
On Memory Palaces & Visual Computation
An Essay by Taulant SulkoI now use Are.na as a Memory Palace, separating my channels into rooms. For example, I have a channel that I call the Computation Room. It’s pretty generic and includes any type of block that relates to computation.
If I notice a pattern in the computation room I create a more specific channel in that room. I think of that more specific topic as an object within the room.
Then there are the adjacent topics that I often find even more exciting to focus on. For those, I choose a name that corresponds with the nature of a room and also its size. For example I have a channel called the Visual Computing Observatory. In my head I am imagining an actual observatory where I am looking and observing and studying a given topic.
The Method of Loci
An ArticleFrom the time we learn to walk, we start building up spatial memories—recollections of the layouts of physical spaces and their relationships to the objects in them. These memories tend to form fast and stick around for a long time.
The method of loci hijacks our innate aptitude for remembering physical spaces, using it to help us remember other kinds of information with greater ease.
Derrière les fagots
A DefinitionA fagot is a bundle of branches tied with a string. They used to be kept in a corner of a barn or shed, and people used to hide things (wine, valuables, etc) behind them often for a long time, and forget about them. It is a way of saying that [a thing] is very good, but has been forgotten for a long time and recently re-discovered.
Nototo
An ApplicationThe visual workspace for notes. Humans have incredible visual-spatial memory. Leverage that with Nototo.
Art is memory's mise-en-scène
A QuoteRe-learning to learn
An Article by Erica Heinz- 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)
Walking through doorways causes forgetting
A Research PaperEntering or exiting through a doorway serves as an ‘event boundary’ in the mind, which separates episodes of activity and files them away. Recalling the decision or activity that was made in a different room is difficult because it has been compartmentalized.
That the mind may not be taxed
A Quote by Thomas FarnabyIn 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.
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.