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.
What's Wrong With This Model?
What's wrong with the rational model
- We Don’t Really Know the Goal When We Start
- We Usually Don’t Know the Decision Tree – We Discover It as We Go
- The Nodes Are Really Not Design Decisions, but Tentative Complete Designs
- The Goodness Function Cannot be Evaluated Incrementally
- The Desiderata and Their Weightings Keep Changing
- The Constraints Keep Changing
Deciding what to design
We Don’t Really Know the Goal When We Start
The most serious model shortcoming is that the designer often has a vague, incompletely specified goal, or primary objective. In such cases, the hardest part of design is deciding what to design.
I came to realize that the most useful service I was performing for my client was helping him decide what he really wanted.
Today, we recognize that rapid prototyping is an essential tool for formulating precise requirements. Not only is the design process iterative; the design-goal-setting process is itself iterative. Knowing complete product requirements up front is a quite rare exception, not the norm. Therefore, goal iteration must be considered an inherent part of the design process.
Evaluating goodness
The Goodness Function Cannot be Evaluated Incrementally
The Rational Model assumes that design involves a search of the decision tree, and that at every node, one can evaluate the goodness function of several downward branches. In fact, one cannot in general do this without exploring all the downward branches to all their leaves, which is possible in principle, but leads to a combinatorial explosion of alternatives in practice.
Changing constraints
The Constraints Keep Changing
The explicit listing of known constraints in the design program helps here. The designer can periodically scan the list, asking, “Can this constraint now be removed because the world has changed? Can it be entirely circumvented by working outside the design space?”
They just don't work that way
Perhaps the most devastating critique of the Rational Model, although perhaps the hardest to prove, is that most experienced designers just don’t work that way.
“Conventional wisdom about problem-solving seems often to be contradicted by the behavior of expert designers. Empirical studies of design activity have frequently found ‘intuitive’ features of design ability to be the most effective and relevant to the intrinsic nature of design. Some aspects of design theory, however, have tried to develop counter-intuitive models and prescriptions for design behavior.” — Nigel Cross
We must outgrow it
Why all this fuss about the process model? Does the model we and others use to think about our design process really affect our designing itself? I believe it does. I believe our inadequate model and following it slavishly lead to fat, cumbersome, over-features products and also to schedule, budget, and performance disasters.
The Rational Model, in any of its forms, leads us to demand up-front statements of design requirements. It leads us to believe that such can be formulated. It leads us to make contracts with one another on the basis of enshrined ignorance. A more realistic process model would make design work more efficient, obviating many arguments with clients and much rework.
The Waterfall Model is wrong and harmful; we must outgrow it.