It is still useful to memorize the flashcards. The terminology provides hooks that will remind you of the conceptual framework later. If you want to practice actually recognizing the design patterns, you could read some of http://aosabook.org/en/index.html and actively try to recognize design patterns. When you want to learn to do something, it’s important to practice a task that is as close as possible to what you are trying to learn.
In real life when a software design pattern comes up, it’s usually not as something that you determine from the code. More often it’s by talking with the author, reading the documentation, or inferring from variable names.
The strategy described in http://augmentingcognition.com/ltm.html, assuming you have read that, seems to suggest that just using Anki to cover enough of the topic space probably gives you a lot of benefits, even if you aren’t doing the mental calculation.
It is still useful to memorize the flashcards. The terminology provides hooks that will remind you of the conceptual framework later. If you want to practice actually recognizing the design patterns, you could read some of http://aosabook.org/en/index.html and actively try to recognize design patterns. When you want to learn to do something, it’s important to practice a task that is as close as possible to what you are trying to learn.
In real life when a software design pattern comes up, it’s usually not as something that you determine from the code. More often it’s by talking with the author, reading the documentation, or inferring from variable names.
The strategy described in http://augmentingcognition.com/ltm.html, assuming you have read that, seems to suggest that just using Anki to cover enough of the topic space probably gives you a lot of benefits, even if you aren’t doing the mental calculation.