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.
Why Software is Slow and Shitty
Roman empire military
Rome military diagram.
Most company structures are based on the Roman empire military. CEO Caesar says he wants something, and the lieutenant managers below him on the org chart break it down into smaller tasks for the soldiers to accomplish.
On a development team, programmers are the soldiers of these shitty new armies. They open their Jira issues and add whatever feature it says to add, or fix what it says to fix. If I can save time by adding another dependency, or skip a meeting by implementing a mockup exactly as designed, why should I care?
Building is never a straight line
You might think that Mario 64 was built with tickets and sprints, but, according to interviews, there was no master plan, only the principles that the game should feel good and be fun. They started with just Mario in a small room, and tuned his animations and physics until he felt nice and responsive. After that, the levels were also created as they went, with the designers, developers, and director going back and forth using sketches and prototypes.
Building like this is never a straight line. Ideas and code get left on the cutting room floor because part of innovation is questioning whether what you made should exist. The process is cyclical and iterative, looking something like this.
Conversations, not commandments
Good software comes from a vision, combined with conversations not commandments. In a craft-focused environment, care for efficiency, simplicity, and details really do matter. I didn’t leave my last job just because I wanted to make something new. I left because I wanted to make it in a way I could be proud of.