Is it normal to forget most of a CS50 problem the next day?

You don’t need to memorize a whole solution. Aim to understand what each part is doing and why it’s there. Being able to explain the logic in plain language is a better test than reproducing every line from memory.

Try changing one detail in the problem, then work out what would need to change in the program. That helps show whether you’ve picked up the pattern rather than just followed a recipe.

Next time, make the first attempt yours, even if it’s messy. Write down what the program needs to do, split that into small steps, and try each step before asking for help. If you get stuck, look for a hint about the specific part, not a complete solution.

AI can be useful for explaining an error or asking you questions about your approach. But if it supplies the structure and code, you may finish the assignment without getting much practice making those decisions yourself.

Do a small recall session after a break, not a full memory test the next morning. Close your notes and write down the main idea, then check what you missed. A day or two later, try a tiny variation of the problem. Short repeat attempts are easier to sustain than spending hours trying to force a perfect rebuild.

For a pattern problem, work through a few small inputs by hand first. Write down what the output should look like, notice what changes between rows or steps, then describe the rule in ordinary words. Once that makes sense, turn the rule into code.

Looking up syntax is fine. The useful thing to practice is deciding what the program needs to do and how to break it into pieces.