iTranslated by AI
Forgetting Almost Everything I Read
The Reader Without Memory
I love books, but I struggle with a poor memory; I am troubled by the fact that the content slips away from me almost immediately after I read.
Within a week, the plot becomes hazy, and a month later, I only have the faint recollection that I "think" I read it.
If that is the case, is there any point in my reading?
However, I would like to argue here that forgetting what you read might not be as bad as you think.
Forgetting is Not a Flaw
When standing before a book, it is easy to become obsessed, thinking, "I can't remember this because I lack the ability." (I am sure I am not the only one who feels this way.)
But there are things you can do precisely because you forget.
For example, you can read the same book again and again with a fresh perspective. You might underline different passages than you did before, or react to different words. If you remembered everything, this would not be possible.
Even if you forget the specific plot, the "gold dust" received from the book often remains. (As in the words of Osamu Dazai.) It is something difficult to put into words—like a perspective on things or the sensation while reading—and as the memory fades and becomes abstracted, that gold dust gradually accumulates within you.
Whether or not you remember the text does not necessarily correlate with whether or not it has become part of your flesh and blood.
Let Go of Obsessions and Mismatched Books
If you convince yourself that you "must keep the characters' names, the plot developments, and the author's arguments all in your head," reading itself becomes a painful chore.
We are not studying for an entrance exam.
If we can retain the simple feeling that it was interesting, isn't that enough even if we don't remember the whole content?
Perhaps we demand too much from books. We feel we must gain knowledge, cultivate our intellect, and find guidelines for life. Books burdened with such expectations become heavy to open.
In truth, it is fine to be more casual. Open a book on the train or bus, and if it doesn't fit, close it.
When you cannot understand something, it is not always due to your own lack of ability. Sometimes the content itself is difficult, or the order of the explanation is just not right. There are also days when you are simply tired.
It is perfectly fine not to read until the very end, or to just pick out the chapters that catch your eye by looking at the table of contents. You should be able to engage with books more loosely.
By the way, on the podcast "Yuru Gengogaku Radio" that I like, they described this mindset as "becoming a gal." In short, I think it means staying light-hearted. Be polite, but don't pander; if it feels like a mismatch, walk away. That is far healthier than holding onto a book you couldn't understand and blaming yourself.
The Same Goes for Technical Books
Everything mentioned so far applies to books in general, but the situation is no different when reading technical books or documentation.
We engineers read many technical books. Yet, details like syntax and function arguments rarely stick, and we end up looking at the documentation every time anyway. What remains is a rough sense of direction—knowing that in this kind of situation, there is a way to handle it. Even if you forget the specific code, the outline of the thought process remains. It is the same as the idea mentioned earlier about abstracted things accumulating.
Therefore, I don't think you need to feel pressured to remember everything in a technical book either. Read it through once, leave markers where you got stuck, and refer back to it when necessary.
Compatibility with explanations varies greatly from book to book, and it is often faster to switch to another book or the official documentation rather than enduring a technical book that doesn't fit.
A Reading Method That Presumes Forgetting
As a specific trick I've used recently, I have a method of "just folding the corners of the pages." I fold the top corner of pages that interest me and keep moving forward. I don't use bookmarks or take notes on the spot (as these are difficult to do while on a train or bus). Since it's a book I bought myself, I have the right to fold the pages.
It's fine to revisit the folded corners when you're in a quiet place, after finishing the book, or even days later. Often, I find myself unable to remember why I marked a particular spot. That doesn't matter, though. As long as I can pick up the words I need at that moment, the purpose has been served.
Another thing, which is slightly different from a reading method, is to write a short impression after reading. Rather than to help me remember, I feel that the act of writing itself leaves a little bit of that gold dust in my hands.
(Conclusion) Reading is Meeting Those Words in That Moment
I will eventually forget the contents of the books I read. I believe that is fine.
Because I forget, I have empty space to accept new things.
Because I forget, I can make different discoveries from the same book over and over again.
Reading is not about memorizing.
It is about meeting those words in that moment.
And that encounter, even if forgotten, will surely change you.
Sometimes, I suddenly recall a passage from a book I read long ago.
I don't remember the exact text, but the sensation of it remains.
That is enough for me now.
If you have anything to share, please feel free to contact me on X.
Discussion