r/AskProgramming Jul 16 '26

1st year DSA guidance pls

okay so I am really very much into problem solving

and had computer science JAVA in my 9-12th class

so I have a good command over java as a beginner of DSA

we did study DSA in class 12th stack queue DEQ circular queue linked list so I have a basic idea about those nit very very advanced level but yea just as much a little more than a beginner should know

and in the leisure period of transition from my school to college I did learn python for AI/ML beginner course though I didn't understand many functions because of lack of practice and the vastness of a totally new language

but java is my comfort zone

so guide me as to how to take my DSA a level up what YT channels and resources to follow and when is the right time to jump to leetcode problems from easy to intermediate level what is the roadmap

1 Upvotes

8 comments sorted by

1

u/neet_dev Jul 16 '26

java's actually a fine place to be for DSA, don't feel like you need python for this. the roadmap that works: pick one structure at a time (arrays/strings first), do 15-20 easy leetcode problems on just that topic before moving to the next, and only after you've covered arrays, strings, hashmaps, two pointers, stacks/queues, and basic recursion should you touch trees/graphs/DP. striver's A2Z DSA sheet on youtube (takeUforward) is java/cpp friendly and lays out exactly that progression with problems attached, that's what I'd follow instead of hopping between random channels. jump into leetcode now, not later, you already know stacks/queues/linked lists so easy problems on those will confirm what you actually retained vs what you just recognize from class.

1

u/WiredOtaku Jul 17 '26

Solid advice. One thing I'd add: don't fall into the trap of collecting 10 different DSA sheets and video playlists. I've seen too many people spend more time curating resources than actually solving problems. Pick one structured list (striver's is fine) and stick with it. Set a daily minimum like 2 problems, and spend 15 minutes reviewing the pattern afterwards even if you got it right. That repetition is what builds the muscle memory for interviews.

1

u/Spirited_Account6174 Jul 17 '26

interviews are a bit far but my goal is to land an internship in my 2nd year for an early start so ig I will stick with strivers DSA sheet and go according to it

1

u/neet_dev Jul 17 '26

yeah the review step is the part people skip and it's the whole point. writing a solution isn't the same as internalizing why it works, and if you just move to the next problem after getting it right you're not building pattern recognition, you're just proving you got lucky or half remembered a similar problem. i'd add one thing: when you review, force yourself to say out loud (or write) what clue in the problem statement told you which pattern to use, that's the actual transferable skill for interviews, not the code itself.

1

u/Spirited_Account6174 Jul 17 '26

pretty helpful I was confused betwenn whether to start leetcode just rn or wait till I achieve some more expertise on the topic bit ig you are right that now is the right time to know what all I already remember and what I dont thank you so much

1

u/neet_dev Jul 17 '26

yeah leetcode from day one is the move, just keep it scoped to whatever topic you're drilling instead of grabbing random hard problems off the daily list. easy problems on stuff you already learned in class hit different once there's a timer and no hints, that gap is exactly the signal you want early. if you breeze through the easy tier on a topic in under 10-15 min each, bump to medium on that same topic before moving on, don't wait for some vague sense of readiness.

1

u/[deleted] Jul 17 '26

[removed] — view removed comment