RobertJasiek wrote:Understanding generates memorisation.
This is so, and when I was learning go I avoided memorization. For instance, when I started studying a joseki dictionary I started on the large knight's response to the knight's approach to the 4-4, because nobody still played it and I would not be tempted to memorize it. When I started studying tsumego with the Maeda series, once I got through the problems that were appropriate for my level, I waited weeks or months before going back to them, so that I would not just remember the answers, but would have to work out a lot of them again.
However, I now think that there may well be a place for memorization in go. Ancient memory methods relied heavily on imagery. It is quite possible that the poetic names for some ancient problems and tesuji acted as aides memoire.
RBerenguel wrote:Rote memorisation can only get you so far, and, in general, memorisation using more effective tools gets you to the same place somewhat faster. Probably the best areas where memorisation is useful is joseki, fuseki and endgame (just like in chess, actually) but like in chess, knowing the main line gets you nowhere unless you can justify the moves to a deviating opponent.
An important point. If you understand the joseki you know how to handle the deviations, and you know that you know that. Why memorize sequences?
RBerenguel wrote:Spaced repetition for tsumego only works because you are doing a lot of tsumego, not because of remembering (more or less.)
A good point, but I would not be too sure of that. One learning technique that I used was overlearning, by solving problems that I had already solved. IIUC, spaced repetition is a form of overlearning.
The overlearning technique that I used works this way. Suppose that it takes N tries to a problem before success. After that you overlearn the problem by adding N/2 more successes. I kept track of successes by Xs and failures by check marks. (I also crossed through a check mark to make an X, after the first success.) Sometimes I waited so long between repetitions that I failed on problems that I had succeeded on before.

RBerenguel wrote:There's not much point in trying to find coding ways (peg methods, memory palaces, etc) for go positions (or chess positions.) Chunking should happen naturally, where the code is the position.
I quite agree. For fun I wondered how to construct mnemonic images for a joseki sequence. For instance, let the image for the 3-4 point be three mice running through a door, and the image for the 5-4 point be a hive of bees over a doorway, etc. Now make up a story for a joseki sequence. Are you kidding?
I do think that language is good for organizing, understanding, and memorizing go positions and plays. If you really understand go terminology it is hard not to be a good amateur player.
