Using memory techniques (mnemonics) to master languages/frameworks/libraries/documentation?

Question

Programming

I couldn't find any articles/books specifically on this topic.
Using memory techniques (mnemonics) to master languages/frameworks/libraries/documentation?
Do you have experience, or someone you know, with application experience?
Are there any results?
======================
UPD#1 I will
clarify and detail the question:
If you used memorization techniques (mnemonics) to master languages/frameworks/libraries/documentation, then share please, how does it feel? What are the results? What was used? What did they remember?
If you have friends who used it and told about it, what did they tell you?
I ask you to share only those who have encountered the subject in experience .
And those who have not experienced it, and believe that it is impossible / not worth it / harmful / not right / not necessary / etc. to speed up learning with the help of memory development:
Please keep silent.

Answer 1

So far haven't found anything.
Are there more examples?
Colleagues, the question will never be closed.
If you have examples, results, familiar methods - please write.
=======================================
Java - https://ankiweb.net/shared/decks/java
Python - https://ankiweb.net/shared/decks/python
.. then I will add to the list
Also, I found :
Used the OpenSource program Anki.
The basic technique is spaced repetitions.
It is based on the concept of the memory curve.
Blog article https://sivers.org/srs
Same program. The same technique.
Blog article www.jackkinsella.ie/2011/12/05/janki-method.html
5500 memory cards - https://www.oxbridgenotes.com/other/web_developmen...
Ruby (1.9)
Ruby on Rails (3.2)
Unix - command line API and OS fundamentals
HTTP protocol
RSpec
Design patterns, refactoring, code smells, functional programming, object-oriented-programming, best practices
Git version control
JavaScript
CoffeeScript
CSS
HTML5, including the canvas, geolocation and web workers
jQuery
Regular expressions
VIM
TDD theory
Web development issues (deployment, caching, etc.)
Backbone.js
SQL
Same program. The same technique.
Blog article www.bryanbraun.com/2013/10/12/learning-drupal-with...

Answer 2

A strange question...
Memorizing too much, in detail, at least in terms of programming languages, libraries, is not only not useful, but frankly harmful . Especially when there are several of these languages ​​used, and the head is a complete mess ...
Understanding is needed, not memorization.
And for everything else, especially at the present time, there is a). help systems and b). archives of their own previous developments, where you only need to know where to "write off".

Answer 3

Mnemonics are usually used to memorize data that is or is not of normal associative structure, such as a list of irregular verbs. Or ones that require precision, such as long strings of numbers.
In programming, there are not so many keywords in any language, any IDE helps to supplement the syntax, and remembering the specific syntax of certain libraries and the meaning of classes is of little use due to the fact that they are updated and support method overriding.
Therefore, instead of mnemonics, they usually use cheat sheets with short examples of commands or blocks, which, with the material studied, help much better.
Very few useful things in programming can be learned through mnemonics, and several hundred programmers I know have never used mnemonics specifically for programming. For English, yes.

Answer 4

Well, why? With frequent use, everything is remembered by itself. And if you rarely use it, then why not look at the docks?

Answer 5

Wow, you're brainwashing yourself.
You need to memorize what cannot be logically calculated, and what needs to be applied in real time and very quickly (like English).
You have already been rightly told that you need to look at reference materials and your own developments. But no, you stubbornly fence your line. Do you want to turn your brain inside out?
Programming is not English. Speech and writing are applied quickly, almost instantly, during the conversation there is no time to look into dictionaries and grammar, plus it is impossible to logically calculate the translation of a word. That is why you need to keep all this in your head and memorize it.
Another thing is programming languages. It is important to understand the principle of operation, everything is based on logic, and is applied only when you run the code. It takes seconds to look at something obvious but forgotten in reference material. If necessary, you can delve into the help, and remember (learn) exactly as much as you need at the moment.
IMHO, by cramming, you will waste time that could be spent on something more important.

Answer 6

Are there any results?

There are results without it. The main rule: if you have to look for ways to memorize, then you are going through material that requires deep immersion too superficially. There is nothing worse than a superficial knowledge of a little of everything.

Answer 7

I listened to a podcast, its author is a programmer and, as I understand it, he studied using mnemonics - a podcast