The Case for Solving the Same Problem Twice

The instinct once you've solved a problem is to mark it done and move to the next one. Revisiting it later can feel like wasted time — you already know how, so why spend a rep proving something you've already proven?

That instinct works against how skill retention actually works. Solving something once, while it's fresh, mostly tells you that you could do it under the easiest possible conditions. Whether it actually stuck is a separate question, and repetition (specifically repetition spaced out over time) is the only real way to answer it.

Solving something once proves you can do it under ideal conditions

Right after learning a concept, with it fresh in your head and the explanation still fully loaded in short-term memory, you have the best possible conditions to solve a related problem. That's exactly why solving it once, right then, is the least honest test of whether you'll still be able to do it cold, weeks later, under actual pressure.

What spaced repetition actually buys you

This is one of the more reliably reproduced findings in learning research: testing yourself again after a memory has had a chance to fade a little strengthens long-term retention more than repeating something again immediately while it's still fresh. The slight difficulty of retrieving something that's started to fade is exactly what makes the retrieval stick harder the next time.

What this looks like in coding practice specifically

• Solving a problem in a focused session, then again cold a week later. The second attempt is what actually reveals whether the skill stuck or just felt solved in the moment.
• Noticing you hesitate on something you solved instantly last time. That's real, useful signal about where you're actually weak, not a sign the earlier practice was wasted.
• Revisiting a concept across more than one language. So the underlying reflex transfers instead of staying tied to one syntax you happened to practice it in first.
• Letting a solved exercise resurface occasionally instead of retiring it forever. That's the version of practice that actually holds up months later, under real pressure, not just in the session where you first got it right.

This isn't busywork

It's tempting to treat repetition as something only beginners need, and novelty as the mark of real progress. In practice it's closer to the opposite: novelty tells you what you can figure out once, while deliberately revisiting what you've already solved is what tells you what you can actually rely on.

This is also why SoloScript's practice loop deliberately resurfaces exercises over time rather than treating "solved once" as "done forever" — so the spaced repetition that actually builds retention happens by default, not as extra work you have to remember to schedule yourself.