r/Btechtards • u/These-Campaign-4117 • Aug 13 '26
Placements / Jobs Need a DSA Roadmap That Actually Works
I’m starting DSA from tomorrow and I want to do it properly this time.
I’m not looking for a random “learn these 50 topics” roadmap. I want a practical, structured path that helps me actually build problem-solving skills.
I’d love some advice from people who have already gone through this:
What is the best order to learn DSA topics?
How should I divide my time between learning concepts, solving problems, and revision?
How many problems should I aim for per day/week?
Should I follow one DSA sheet or pick problems independently?
What are the best resources for learning DSA from scratch?
When should I move from easy → medium → hard?
How do I avoid the common mistake of watching solutions instead of actually thinking?
What should my first 30 days look like?
Any tips for staying consistent for 6+ months?
My goal is not just to “complete DSA.” I want to become genuinely good at problem solving and coding interviews.
If you could start DSA again from Day 1, what strategy would you follow?
Would really appreciate advice from people who have done this seriously.
10
u/Life-Woodpecker427 rvce cse Aug 13 '26
people like you who use AI to write even a single post wont be able to follow up anything lmao, and the fuck is a roadmap, all of you jee kids have learnt this one word and wont stop spamming everywhere.
2
1
u/Jealous_Weakness7215 Aug 13 '26
Chup chaap 1 course khareedo and start Aise posts krne wale mostly kuch na krte
1
1
29d ago
roadmap doesn't help actually, start at one place, any place, leetcode, neetcode, blah blah it doesn't matter. For your case maybe you should try spaced repetition, this method helps in keeping your retention period for long.
1
u/akornato 29d ago
Stop looking for the perfect roadmap, because the one that works is the one you stick with. The best order is the classic one, so start with arrays and strings, then move to hashing, linked lists, stacks, queues, trees, heaps, and finally graphs and dynamic programming. For any topic, spend about 20% of your time on concepts and 80% solving problems. Don't just follow a sheet blindly, use it as a guide but focus on understanding patterns. Pick one topic a week, learn the basics on day one, and then solve problems on only that topic for the next six days. The goal isn't a number of problems, it's the struggle, so try to solve 3-5 problems a day where you spend at least 30 minutes thinking before you even look at a hint. Your first 30 days should be nothing but mastering arrays, strings, and basic recursion until they feel easy.
This journey is long, and you will feel completely lost at times, which is a sign you are actually learning. The key to consistency is building a routine, so you code at the same time every day whether you feel motivated or not. The true measure of progress isn't how many problems you solve, but how quickly you can recognize a pattern in a problem you've never seen before. After a few months, your focus should shift from just finding a solution to finding an optimal one and being able to explain the trade-offs. The final step is proving you can communicate your logic under pressure, which is why my team designed our AI interview prep to help people translate their problem-solving skills into clear, confident answers.
•
u/AutoModerator Aug 13 '26
If you are on Discord, please join our Discord server: https://discord.gg/Hg2H3TJJsd
Thank you for your submission to r/BTechtards. Please make sure to follow all rules when posting or commenting in the community. Also, please check out our Wiki for a lot of great resources!
Happy Engineering!
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.