I'm a first-year computer science student who started learning Data Structures and Algorithms (DSA) using Java this past October. It's been about two and a half months, and I've tackled over 20 pattern questions (like star and alphabet patterns), more than 30 array problems, and 13 binary search questions. I make it a point to revise all the problems and concepts every Sunday, but I'm struggling to retain what I've learned, including the notes I've made. I find myself taking around 30 to 45 minutes on easier problems, and sometimes up to two hours on tougher ones like finding duplicates or merging intervals. I'm feeling frustrated because I want to improve my problem-solving skills. Is there a way to overcome the challenges I'm facing? I'd really appreciate any advice!
4 Answers
It's totally normal to find DSA tough, especially when you're just starting out. Aside from just solving problems, it's super important to understand the theory behind them. Instead of rote memorization, focus on the concepts and the reasons behind the solutions. That way, you'll build a deeper understanding that helps you remember better.
You're probably focusing too much on predefined problems. To learn DSA effectively, you should: 1. Study the theory, 2. Implement it, 3. Solve related problems, and then 4. Review and repeat. Once you're comfortable with the concepts, then tackle random problems. If you get stuck, don't hesitate to revisit the theory!
Does step 4 mean specifically learning techniques like binary search or two pointers? I didn’t quite catch step 5.
It sounds like you're mixing problem-solving sites like LeetCode with your DSA studies. Remember, DSA involves understanding abstract concepts and how to manipulate data effectively, while platforms like LeetCode are just a way to apply that knowledge. Make sure you're dedicating time to study the theory separately before jumping into solving specific problems.
Do I really need to learn from textbooks? I'm just trying to get better for job interviews.
The key is to keep practicing but try not to spend more than 2 hours on any single problem. When you're stuck, look at the solution only for guidance—then code it out on your own. Turning the idea into your own code is what really helps with understanding and memory.
I’m not sure about looking at solutions, though. Isn't it better to figure things out myself?
Let me try that method out!