The _main_ goal is to never have to look into that crappy pdf again, which eats way too much time and so is in effect very bad for repetition. Here follows my m

The _main_ goal is to never have to look into that crappy pdf again, which eats way too much time and so is in effect very bad for repetition. Here follows my method. I don't learn much at all this way before tests. If you do understand enough and the topic is knowledege-based (not example based like code or math) you can write down the structure alone and do lookups into the organizers' pdf if you forgot a point. This is like a map where the key points are put down in collections. Key points can have explanations/clarifications too: Java Agent. Interpreter-feature. or Dynamic. Modifcation & addition. Example for java code analysis: https://pastebin.com/HZRReG1W https://pastebin.com/HZRReG1W Note: It fails where examples/code/math is needed. I'll probably write my own app one day, but what I imagine is the best way includes versioning, learnability, sharing etc which makes the endeavor quite complicated due to sheer the amount of moving parts. The ability to learn anything is too good a dream though so I cant give it up ever haha!