I've started working on my own code specific flashcard program. The algorithm, app, and cards are one part of the app, and the other part of the app -- the actu

I've started working on my own code specific flashcard program. The algorithm, app, and cards are one part of the app, and the other part of the app -- the actual cards -- is whatever application you want. Basically, I wanted a flashcard app mashed together with repl.it. At first I thought I'd just have the python interpreter built in, but I slowly realized that correctly implemented flashcard is a programming template and a correct answer, and that your choice of interpreter should produce the correct answer given your input. --- So now I've come to the general formulation of the app: Question -> Some application specific file. For Python it might be the boilerplate into which you insert a nested list comprehension. For C# it could be a whole project boilerplate into which you insert your LINQ statement. Answer -> The expected output when your program is done executing. Probably on STDIO? Maybe something else. There are lots of IO options in an Linux OS. Card -> Question, Answer, Executable (we could probably infer this from the "question" card) --- Everything after this would be pretty much like Anki as it is now. You could have a script that listens to you play a song and then scores your performance. You could take touch/writing input and score penmanship. And so on. The possibilities here are limited by your imagination. Unfortunately, I got derailed trying to sort out the review algorithm. If anyone has any ideas on this front, I'm all ears. I know Anki's algorithm punishes skipping review days, and I'm one who skips review days frequently. Which leads to me quitting altogether because the review load becomes boring and unbearable.