I see a screenshot there defines an anki card? Couldn't find any mention about anki in docs or on the github (I only skimmed though). Would be interesting to see if there is a possible interplay.
I myself use vanilla org mode for this purpose (spaced repetition). My workflow is the following:
1. Create a hierarchical structure with leaves representing
bits of knowledge. For example postgres/indexes{btree, GIN, ...}
2. Have a study session with materials (books, video, etc).
3. Try to recreate a concise version of each subject and place it under leaves, so put text in btree, GIN, etc. If I cannot do something I skip it and fill as much as possible.
4. Verify written, fix if necessary.
Then, the document will sit there for a while and when I feel that I need to review a certain subject I would open a tree node and try to recall the child nodes, or sometimes go directly to leaf nodes and try to explain each. Then verify with the data there, maybe do additional research if something isn't clear.
I initially wanted to make anki cards for every piece of information that goes to leaf nodes, but it seemed that hierarchical organization suits me better. It would be interesting to try an automatic card system that would keep track of when I reviewed the concepts and remind me to do so.
The example in the screenshot uses anki-editor which lets you write anki cards in org-syntax anywhere in your knowledgebase and then sync them with your Anki.
As org-roam itself is not a spaced-repetition tool it does not mention that particular setup in the docs. IMO, the one thing that none of the alternatives to org-roam offers is a (very) vast ecosystem of packages. As your notes are just org files underneath, org-roam plays really well with any other org-mode package.
Wow, that resembles something I wanted to implement myself. It's crazy how most of the things you think of doing are already done.
I think I will migrate to it eventually, thank you.
> I see a screenshot there defines an anki card? Couldn't find any mention about anki in docs or on the github (I only skimmed though). Would be interesting to see if there is a possible interplay.
I saw that too! I love the idea of using Git and an editor to manage my Anki cards.
I myself use vanilla org mode for this purpose (spaced repetition). My workflow is the following:
1. Create a hierarchical structure with leaves representing bits of knowledge. For example postgres/indexes{btree, GIN, ...}
2. Have a study session with materials (books, video, etc).
3. Try to recreate a concise version of each subject and place it under leaves, so put text in btree, GIN, etc. If I cannot do something I skip it and fill as much as possible.
4. Verify written, fix if necessary.
Then, the document will sit there for a while and when I feel that I need to review a certain subject I would open a tree node and try to recall the child nodes, or sometimes go directly to leaf nodes and try to explain each. Then verify with the data there, maybe do additional research if something isn't clear.
I initially wanted to make anki cards for every piece of information that goes to leaf nodes, but it seemed that hierarchical organization suits me better. It would be interesting to try an automatic card system that would keep track of when I reviewed the concepts and remind me to do so.