0% found this document useful (0 votes)
7 views

Guide

The document provides guidance on effectively learning Data Structures and Algorithms (DSA), emphasizing the importance of not overthinking language choice, focusing on interlinked topics, and prioritizing quality learning over speed. It advises against comparisons with others, encourages continuous practice, and suggests sticking to one resource for better productivity. Additionally, it motivates learners to remain persistent and dedicated for a successful career in software engineering.

Uploaded by

Jaswanth Kumar
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
7 views

Guide

The document provides guidance on effectively learning Data Structures and Algorithms (DSA), emphasizing the importance of not overthinking language choice, focusing on interlinked topics, and prioritizing quality learning over speed. It advises against comparisons with others, encourages continuous practice, and suggests sticking to one resource for better productivity. Additionally, it motivates learners to remain persistent and dedicated for a successful career in software engineering.

Uploaded by

Jaswanth Kumar
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

1.

DON'T WASTE TOO MUCH TIME ON CHOOSING THE LANGUAGE:

"You need to check how many optimized solutions are you able to think?"
You able to think:
Q. Which Data Structure will be used?
Q. Which Algorithm will be used?
Q. How much time will be required?
Q. How much space will be required?

Like that we have to start thinking of great solutions.


Any Language will do, just a big push. Do Some Functional loops, OOPs in it and
just learn them to get Ace in DSA

"" PROGRAMMING LANG + DSA = AWESOME VALUE** ""

2. DON'T STICK TOO MUCH ON SINGLE DSA:

NO NEED TO SOLVE EACH TOPICS OF 100 PROBLEMS..


SOLVE THE QUESTIONS ON DIFFERENT IDEAS IN EACH TOPIC ATLEAST 20-30 QUESTIONS ONLY..
BECAUSE YOU NEED TO COVER EVERYTHING AND TOPICS ARE "INTER-LINKED" LIKE THIS:

TREES ---> RECURSION ---------}


STACKS & QUEUES ---> LINKED LIST }===interlinked topics
GRAPHS ---> STACK & QUEUES -------------}

it takes 4-5 months with more consistency to complete DSA and goes on till..

3. DON'T RUSH TOO MUCH ON PROBLEM SOLVING:

"YOU NEED TO HAVE QUALITY LEARNING"

" you don't need to make the question solve within 15-20 mins and go for next
question"
(This is WRONG... XXXXXX)

"you will have to give some time, apply your brain, think from an approach, discuss
with your friends"
YOu have to think "What can be done it, can i add some recogninition to do this"
FOR THAT USE ""PEN & PAPER"" and try to go for idea

If you are unable to solve then try again and try again... still you are
struck..approach to solution and learn from the idea have used in it..and "bookmark
the question" ***

try to learn new concepts and apply the approach and you may able to solve 200-250
problems in the end of the months and can spend time but not more a very little
time need to spend and solve new concepts

4. DON'T DO COMPARISON WITH OTHERS:

Because Everyone has become a software engineer, Everyone has become a DSA.
You have to learn well and What is the diff b/w your friend learned it in 4 months
and you have learned it in 8 months?
What matters is "who has learned it well", "who is solving the problems well"..IT
DOESN'T MATTER THE TIME YOU TAKEN AND IT IS NOT LIKE AN IIT EXAM (YOU NEED TO WRITE
YOUR EXAM IN ONE TIME) AND IN JOBS IT DOESN'T MATTER HOW MUCH TIME YOU HAVE TOOK
AND JOBS ARE AVAILABLE EVERY WHERE..SO DON'T BE AFRAID AND FOCUS ON YOURSELF.

They wont say i have done this much and i have gone to reached this far, i am not
even here..THERE IS NOTHING LIKE THAT..and By doing this it demotivates you and
your learning..so dont say to anyone and dont compare with others..

Think as i too will solve this problem well and if you keep thinking this
future..you are able to be do it in right way..

5. DON'T LEAVE DSA AFTER LEARNING:

'DON'T GIVE AFTER LEARNING'


i.e while studying learning web development and i code this and i will leave DSA
(This is wrong approach)

If you are good in DSA try to make the flow or consistency in DSA and
Simultaneously into the Web development also..

once you have learned it...start Solving random problems like 5-6 problems in a
week..

Don't stop the flow continue with solving problems daily or a weekly 5-6 problem or
participate in challenges or contests or solve random problem or daily questions
from DSA..

SO MY DEAR FRIENDS "DON'T EVER PAUSE DSA!!"....Until we make us very strong and get
into the GREAT JOBS..

BONUS TIPS:

6. DON'T SWITCH YOUR RESOURCES:

SO DONT GO MORE TUTORIALS AND DONT GO ALL EVERYTHING FROM EVERY VIDEOS...

THE LEARNING PRODUCTIVITY WILL BE HAMPERED SOON...

YOU WILL NOT BE ABLE TO LEARN ANYTHING..

GRAB ONE LEARN IT WELL, AFTER THAT YOU KEEP DOING ANY RESOURCE, IT DOES NOT
MATTERS, BUT IN THE BEGINNING AT THE TIME OF LEARNING, YOU HAVE TO LEARN ONLY ONE
RESOURCE, IT MAKES YOU PRODUCTIVE AND YOU WILL SEE CONTINUE GROWTH IN IT..

7. DON'T GIVE UP:

REMEBER NOW: IF PERSON WANT TO BECOME A SOFTWARE ENGINEER THEN THAT PERSON HAS KEPT
TIME TO STUDY DSA FOR 6 MONTHS...JUST DO IT!! , & We will not give up on it!!

Motivate yourself for 6 months and do it...even if you are not able to solve
problems..We should not feel regret later and then watch solutions..but learn them
and know how the approach gone..this helps you "keep on learning"...

o/p (PACKAGES, become a software engineer) is very good, you have to pay attention
in your input and your efforts on it!!

If your efforts good then automatically output will keeps you good and high
demand!!

Happy Coding !!

THANK ME LATER : )

You might also like