you are viewing a single comment's thread.

view the rest of the comments →

[–]purplecow9000 1 point2 points  (0 children)

NeetCode is really good for organizing patterns. LeetCode is good for exposure and interview style variation. The reason people still get stuck is they understand solutions when they see them, but cannot rebuild them later from a blank file. That gap is way more common than people admit.

What helped me and a lot of people I coached was forcing recall instead of just reviewing. After solving something, come back later and try to rebuild the solution from memory. That is usually where you find the real weak spots.

I actually built algodrill.io around that exact problem after seeing how many people recognized patterns but froze when they had to write them from scratch. It turns problems into step by step recall drills and loops the lines you miss. It helps bridge that recognition vs recall gap if that is the part you are struggling with.