Is It Normal to Check Solutions for Easy DSA Problems?

It's really common for beginners to misinterpret the wording of a question, which can lead to confusion. When tackling a DSA problem, what’s your usual approach? Do you break it down into smaller parts and think about which concepts apply?

When I'm stuck, I keep a notebook handy. I jot down what I'm not sure about, and I write both the problem and its solution, along with an explanation of why that answer works. This helps a ton for remembering why I chose certain methods. Remember to try solving it first before jumping to solutions—learning on your own is key!

Relying on solutions too soon can be a bit of a bad habit. Ideally, you should only check if you've put in a solid effort to solve the problem for a while. And don’t forget: once you do look at a solution, make sure you fully grasp it before moving on. That way, you can learn from it and not just memorize it.

Getting started with DSA is definitely a process of trial and error! Do your best with the material first, and if you get stuck, consider using tools like AI to get hints that can help shift your perspective. Needing a bit of help in the beginning is totally normal.

You definitely shouldn't feel bad about needing to check solutions sometimes! It's important to realize that looking at a solution can shortcut your learning process. Instead of just seeing the final code, try to understand the journey that leads there—the analysis and choices made along the way. If you're finding yourself giving up too easily, it might just mean you need to build more persistence and discipline in problem-solving.