27 Comments
User's avatar
Ezekiel Kouassi's avatar

Thank you!

Now I Known how to master DSA. Continue sharing, you help a lot.

Ashish Pratap Singh's avatar

Love to hear this, thank you!

Marudhupandiyan's avatar

Nice Picturized bro💯💯

Morvana Bonin's avatar

Thank you for sharing!

Mahmoud's avatar

Thanks so much for this amazing article.

Mohammad Aakash's avatar

Thanks for sharing this. I have started DSA preparation from Today morning and now I got this best guide on how to make it best .

again Thanks for sharing Ashish

Ashish Pratap Singh's avatar

You are most welcome. Glad it was helpful.

Bobate Olusegun's avatar

Awesome, thanks for sharing this. Honestly it helps a lot.

Ashish Pratap Singh's avatar

Great to hear this, thank you!

Amal Murali's avatar

Really helpful! Thank you.

Pavithra's avatar

Yes, thanks for this, I'm starting my DSA journey from today, I hope this helps me in my DSA Journey, as a working professional I hope this helps me land in a better job

Kanaye Varma's avatar

Very nice article! I write about DSA on my stack ( https://kanaye.substack.com ). Personally I think it’s important to learn how to think about solving problems than knowing every single one by heart… so for every data structure you learn try to understand the fundamental reasoning behind why it’s used. You made a nice list, I enjoyed reading it :)

Hung Vo Van's avatar

should I learn follow the order dsa on the post or follow by the tutorial you recommend on this post?

Alok Jha's avatar

Hi Ashish, I am currently working as a data scientist but I know how important DSA is to crack top companies, I find your content really inspiring and helpful. I wonder if you could filter DSA for Data Scientists as well because as far as I know DSA expectations from Data Scientists is different from what is expected from S.Engrs. Thanks in advance.

Mirko Peters - M365 Specialist's avatar

DSA = gym time: progressive overload, not hero PRs.

One-topic sprints, implement-before-import, 5 easy → medium reps, pattern journal, and a ruthless revision list.

Less binge-watching, more code reps; interviews notice the muscles. 💪🧠

Shoeb Raza's avatar

Thanks a lot, this really cleared my doubts 🙌.

Fabiana's avatar

Nice write up!!! I’m also working on DSA and this article was super helpful, thanks!

Dinesh babu's avatar

One thing I want to know is that how much time should I spent on each topic like

1. How many problems should I need to solve ? (Currently I am using Leetcode, there are many problems 100 or more for each topic)

2. You shared a order, I want to follow it. If I keep solving problems for only one topic, I may not complete the order.

So is this process below :

1. Should I follow (Start learning a new topic) i.e 4-5 easy leet code problems

2. After that, move on to next topic

3. After all topics over, then I move on to depth each topic?

Could you please resolve this one?

Ashish Pratap Singh's avatar

hey, yeah the idea is to first get familiar with topics by solving 4-5 easy problems and then go deep on each topic.