Struggling with DSA and Problem-Solving in Python – Looking for a Smarter Way to Learn

[Noor]

I’m currently learning Data Structures and Algorithms (DSA) using Python, with the goal of cracking coding interviews. However, I’m finding the learning process extremely difficult, and I’m struggling to figure out how to approach problems.

Here are some of the specific challenges I’m facing:

1. Understanding the logic: I struggle to understand the underlying mathematical concepts and logical reasoning behind problems.

2. Identifying loops: I often can’t figure out which loops to use (`for` or `while`), where to place them, or how many loops are actually needed.

3. Managing variables: I find it difficult to determine which variables to initialize, when to update them, and how to track their values throughout the solution.

4. Building problem-solving logic: Even when I understand the problem statement, I struggle to convert that understanding into a step-by-step algorithm.

5. Writing code independently: I can sometimes understand an existing solution, but when I try to solve a similar problem from scratch, I get stuck and don’t know where to begin.

Honestly, coding itself feels overwhelming at times.

What I’m looking for

My ultimate goal is to become good enough at solving DSA problems to crack technical coding interviews.

I’d love to hear from people who have faced similar struggles and eventually improved.

- Are there any shortcuts, cheat sheets, patterns, or smart techniques that make DSA easier to understand?

- Is there a systematic approach to identifying loops, conditions, pointers, and variable updates?

- Are there alternative ways to learn problem-solving logic without getting lost in mathematical explanations?

- How can I develop the ability to convert a problem statement into working Python code?

- Are there any resources, roadmaps, or practice techniques that genuinely help beginners build problem-solving skills?

I’m not necessarily looking for shortcuts to avoid learning. I’m looking for smarter ways to learn, recognize patterns, and approach problems without feeling completely lost.

If you were starting from scratch today, especially as someone who struggles with logic and problem-solving, how would you learn DSA for coding interviews?

Any practical advice, personal experiences, learning strategies, or resources would be greatly appreciated\!

[Hannah]

You’re not bad at this. You’re practising the wrong half.

reading code teaches reading. These five moves teach writing.

#	the move	say it like this
1	one sentence, no code	“return the two numbers that add to 9”
2	do 3 items by hand	one row per step, on paper
3	pick the loop	how many times? yes → for, no → while
4	type five lines	each paper row becomes one line
5	break it	empty list · one item · 1000 items

Move 2, for real — two numbers in [2, 7, 11] that add to 9:

9 − 2 = 7   is 7 already seen?  no  → remember 2
9 − 7 = 2   is 2 already seen?  yes → answer

That is the whole algorithm. The code is a transcription of those two rows.

• Stuck 20 minutes? shrink to 3 items → say the rule that stays true → say what you are doing, plainly.

Two places that make it stick

• Exercism · Python — a real person reads your code and tells you what to fix, free.
• Python Tutor — paste your five lines and step through them; you watch each variable change.

the 14-day order · the maths when you meet it · free mock interviews · a timer

Fourteen days, one idea a day — two problems of the same kind each day, in this order:
compare neighbours → remember what you saw → one pass with two fingers → a window that slides → last in first out → cut the list in half → follow a link → repeat on a smaller piece → trees → grids → shortest path → build up from small answers → mixed set → mixed set.

The maths, when a problem mentions it — three phrases, nothing to memorise:
one pass = look at each item once · every pair = for each item, look at all items · halve it = throw half away each step.

Practice like the interview

• Pramp — free peer mock interviews; you interview each other.
• One problem, 25-minute timer, talk out loud the whole time, then write down the first sentence you would say next time.

Two habits that decide it

1. Close the solution and rewrite it. Reading feels like progress; rewriting is progress.
2. One kind per session. Ten random problems teach ten fragments.

Paper first. The code is the easy half.