[DarthMader]

That seems like a waste of flashcards to me, but if it works for you, it works. I would just create one flashcard for front and back. What is a stack in CS? A stack is an abstract data type that's a collection of elements, with two principal operations: pop and push. If an answer's longer than 1-2 sentences then it's time to break it apart into different questions.

[xkfm]

I find it somewhat excessive (and I still make poor cards even my by own guidelines all the time), but I try optimize to make my flashcards as easy as possible to answer according to [1].

Especially in the long run once you get thousands of flashcards, and have a few breaks because of life. A general rule of thumb I go by is that my answer should be shorter than the question.

Even in your answer there's three or four separate parts to it. You have:

1. An abstract data type 2. collection of elements 3. Two principal operations 3a. Pop and push

[1] https://www.supermemo.com/en/articles/20rules

[DarthMader]

Fair enough. I guess I'm pointing out with cloze questions that don't hide all the selected text, you're perhaps making it too easy. I prefer hiding all, showing one. On a test, you might be able to get similar hints but if the understanding isn't there you might be thrown off by different wording. If I'm creating the knowledge for work, I'd rather simplify as much as possible, break up into different parts where necessary, and learn the answer exactly. Relying on additional context is not something I'd do. For those reasons, I'd prefer regular flashcards when possible. The other benefit of a single flashcard is it's easier for organization purposes.