I'm working on spaced-repetition language flashcards app, that shows you variety of card types (sentences, reverse, audio, definition...) and allows you to add vocabulary from content - youtube, ebooks, website reader.
What’s baseless about it? The yearly subscription price is like 20 minutes of work for programmers and many users are spending tens of hours on the app.
Nice to see someone taking the concept of card variations to all concepts.
I'm taking this to extreme with Vocabuo[1] for language learning. For a single word, I have cloze cards, reverse cloze, definition cards, dialogs, audio and a few more.
At some point, I'd like to take the card type into account when calculating the next repetition stage, but that's a bit far into the future.
I'm building a SRS language learning app [1] so I've thought about this topic a bit, but I've come to a conclusion that srs algorithms might be just a nerd optimization obsession. My app has "stupid" 1,3,7,15,30 or something like that intervals, and the reality is that if I know a card, I can swipe it within 2 seconds, and if I just barely know it, I can spend 30 seconds on it.
So optimizing the algorithm such that every card comes at the exact right moment might cause all cards to feel too hard or too easy. I think having a mix of difficult and easy cards is actually a feature, not a bug.
Don’t fool yourself into thinking a suboptimal SRS is going to be optimal at the motivational aspect. If a user needs a self-confidence boost during a flash card session, this should be a design choice, not due to poor performance of the core SRS algorithm.
Choose your SRS algorithm to best predict what a user knows and when they’re likely to forget it.
If your application decides that it wants to throw some softballs, that’s an application level decision. If you care about psychology and motivation, build a really good algorithm for that. Then blend SRS with motivation as desired.
Thank you for the report! I was thinking of redoing the landing page for a while anyway. Are you using a niche browser or something like that? I haven't had anyone experience this issue nor was I able to reproduce it.
I've been looking into FSRS since I'm building a language learning app[1], but I haven't implemented it yet. Can FSRS work if I don't want to have 4 choices - bad, good, hard...? I have found myself to get into a decision paralysis so just bad/good works better for me. Plus I can swipe the cards tinder style! :D
My second reason is that I'm worried about the complexity - both from non-nerdy users perspective and me having to debug it.
Yes. Some months ago, I forget whether it was v5 or maybe before, the 2 button grading approach meant that it actually performed better for users (ie. it performed better for users that explicitly only used two grading buttons).
I don't know if this is replicable with v6, or not. I would be interested to find out!
I’m building a spaced-repetition flashcards app. Unlike the competitors, the cards have audio, images and sentences. Additionally, it is possible to add words from ebooks, websites and YouTube.
I've finished my Bc. in computer science before AI, but even then, sitting through a 1.5h long lecture and reading a textbook was just not the way to learn.
a) better quality lectures were available online - it's much easier to learn linear algebra from top MIT Professor than a random one at my university
b) the text books were absolutely terrible compared to what was available online
I can understand that 20 years ago people were captivated with the physical lectures because it was the only way. Today however, professors are competing with 3blue1brown, Khan academy, pre recorded lectures from top universities and many more great resources. Standing in front of a blackboard slowly going through an unintuitive math proof is just not going to cut it and people will get bored.
In my experience in-person lectures have been a terrible way to actually learn (compared to recorded ones or other ways of learning):
1. Lectures are often not held in front of just a handful of students, but hundreds, where frequent interaction and questioning between student and lecturer becomes practically impossible, awkward and socially intimidating. Sitting between many other students is incredibly distracting, and I've more than once seen students bring binoculars to class, because they sat so far away from the blackboard!
2. Only a small fraction of lecturers are actually good at teaching, of being engaged and engaging, clear and concise, understandable and empathetic. Not to mention nice handwriting or powerpoint style. Being "forced" to listen to someone whose style of teaching you don't understand or don't vibe with sucks.
3. If you lose the thread in a deep in-person lecture, you might as well just leave. If you watch a recorded one, you can rewind as often as you want until you understand it.
4. Lecture hall rooms are often not the beautiful, comfortable, nice places you love to go to that they ought to be (but dilapidated, broken, uncomfortable, tight, stuffy and dirty).
In these contexts, sitting in a lecture hall becomes more hell than heaven. And professors shouldn't expect their students to find their passion while having to endure this.
>1. Lectures are often not held in front of just a handful of students, but hundreds, where frequent interaction and questioning between student and lecturer becomes practically impossible, awkward and socially intimidating. Sitting between many other students is incredibly distracting, and I've more than once seen students bring binoculars to class, because they sat so far away from the blackboard!
Spring's annotations arguably are black magic, but while Spring offers DI, DI is not Spring, and honestly something like Guice is a lot easier to follow since it only does annotation-based DI and not a bunch of other stuff.
Search within your IDE, do a Google search, whatever suits you.
What mentality? And the cognitive load is to RTFM, so that you understand what are you doing. If that leaves any questions you can attempt to do a deep dive. It's not particularly high cognitive load to know that @GET is a get rest endpoint.
How is that different without annotations? Documentation is also your best bet at first in case of a normal library function call. Jumping into that codebase can also be quite involved, depending on what it does.
There was a 'may' in my original comment. It is metaprogramming, so you can't see every usage automatically even with "alien tech" like IDEs, unlike in case of a normal type.
Especially that we are not even talking about own code, but third-party annotations with its third-party consumers. Also, grepping is a pretty standard term, it doesn't necessarily mean literal CLI grep, but go on with your advanced tooling as if no one else would be familiar with an IDE.
ios: https://apps.apple.com/us/app/vocabulary-flashcards-vocabuo/... android: https://play.google.com/store/apps/details?id=world.petr.vok...
reply