I'm currently using SRS software (Anki) to learn more about software development. Instead of trying to memorize facts I am using cards as a cue that it is time

I'm currently using SRS software (Anki) to learn more about software development. Instead of trying to memorize facts I am using cards as a cue that it is time to revise and deepen my understanding of a particular topic. Every time I learn about a new topic/concept/technique I will add a card to my anki deck with the topic name. E.g. Today I have added JS Promises. Then when a topic comes up for review I spend 10-15 minutes reviewing my knowledge and trying to probe my mind for parts I do not understand and trying to link it to, and see how it can be used with, other related techniques. After reviewing I then spend 30 minutes to 1 hour investigating the technique in more depth. At this point I'll try and implement an aspect of it in code or see if I can answer a few problems people are having with the topic on stack overflow. Then I will add a few notes to the card detailing what I have done so that I can make my next "review" of the card more challenging. All up each review for a card takes close to 1.5 hours. I tend to have 1-2 cards come up per day to review. I find it has given me a broad, and usable, understanding of software engineering practice and principles and has made me a better developer. The downside is I feel you will never become a master at these topics using this technique as the time investment per topic is just not enough. I started using it because I found I had an experts understanding of some topics and a very weak understanding of other fundamental areas of computer science and software engineering. E.g. 1000+ hours of crafting complex regular expressions but lacking a proper understanding of the relational model and how a database table join works. I would be really interested to see if there is any literature that examines using SRS in this manner (as opposed to learning simple facts).