> Struggle is overrated compared to repetition and quick correction.
Just to offer a differing view, I would posit the exact opposite: struggle is underrated compared to repetition and quick correction. The latter is prone to blind memorization, and in my experience, many CS interview questions have a core idea or central motif that aren't apparent until after a long thought.
I don't think that either of struggle or rapid repetition are "wrong", but rather, everyone should experiment with both styles and find some middle ground between the two.
> central motif that aren't apparent until after a long thought.
and yet its impossible to figure out a central / repeating motif if you haven't actually done a lot of the same kind of questions.
sitting down and thinking things through is generally the final phase, in which you're improving the most. In order to get there, a varying degree of repetition is necessary.
Just to offer a differing view, I would posit the exact opposite: struggle is underrated compared to repetition and quick correction. The latter is prone to blind memorization, and in my experience, many CS interview questions have a core idea or central motif that aren't apparent until after a long thought.
I don't think that either of struggle or rapid repetition are "wrong", but rather, everyone should experiment with both styles and find some middle ground between the two.