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.
Beyond Artboards
The Pursuit of Lossless Design-Development Handoffs.
Can't developers just see?
We designers love artboards. From rough UI sketches to high fidelity mockups, we see ourselves as visual artists expressing ideas on artboards that have a pre-defined width and height. To start a new project, we declare the size of the artboard in the first step.
What about responsive design? Not a problem! We diligently design on three artboards — one for mobile, one for tablet, and one for desktop — with content elegantly adapting, scaling, reflowing, reordering, and reprioritizing. We proudly hand off the artboards to developers while patting ourselves on the back: this is how responsive design should be done.
After weeks of arduous engineering, the product finally comes out. We find, to our great dismay, that some copy is hanging off the grid, the focal point of the hero image has been cropped out, the font sizes don’t even come close to the type ramp. What went wrong? Can’t the developers just see everything on all those artboards?
Nope.
We are the ones who paved the path
No matter how many screen sizes our artboards account for, some user’s browser will break loose from our prescription. With users resizing, rotating, and zooming the screen, new devices stretching, squashing, curving, and cutting (e.g. the speaker area in iPhone X) the screen, the sizes become infinite. Good luck making an artboard for each one of them.
Artboards are a lossy format. Using artboards in a handoff is a lossy process. When we pitch a finite number of plans against an infinite number of situations. We inevitably get in-betweens. Once there are in-betweens, there are unknowns. Once there are unknowns there is guesswork. Once there is guesswork, there are surprises. Engineers take the path of least resistance. We are ones who paved the path.
Until we get there
- As a designer, learn writing HTML, or better still, semantic HTML. If coding up the entire design is too hard, try coding up one component at a time, and not worrying about CSS. The HTML alone will prove invaluable for developers to understand the content structure. In addition, you are forced to optimize the information architecture as you work out the code from content.
- If coding by yourself is out of the question, pair up with the engineer who will receive the design. Work closely with him or her to prototype the design, validate responsive behaviors, and obtain feedback on the feasibility. Don’t call it an iteration until the design has seen played with in code.
- As a manager for large enterprise, co-locate your designers and developers, encourage interdisciplinary learning, understand that each minute spent on coding before the handoff translates to ten minutes saved from changing and fixing issues after the handoff.
- As a stakeholder in the handoff meeting, give the designer a thumbs-up when he or she demos live code running in browsers in place of mockups on artboards. That’s a design champion you are looking at.