Exciting news! I've dedicated 1.5 years to DSA, guiding and mentoring thousands of students and professionals. "Ha Wo Baat Alg Hai Uski Post Nahi Dali Btaya Nhe" During this thrilling journey, I've connected with brilliant minds in the tech field, learning from their experiences and knowledge.
I've also engaged with International Programmers and learned valuable insights into their problem-solving approaches and strategies.
I personally follow this approach, and many students and professionals also follow for better improvement. So, if you follow, then you'll definitely find a better result. Otherwise, you're already smart.
The right way to improve your problem-solving, and you learn a lot if you try this...
Read the Problem Statement Carefully and try to Understand with Example.
After reading and understanding the Problem Statement, try to solve the problem but...
Try to identify the pattern and link the concept that is relatable to a problem you already solved or learned the concept.
If you find something, then try to solve it.
Otherwise, try to go with a brute-force approach and try to solve.
30 to 45 min is enough for any problem; no need to put in more time if you are not able to solve the problem.
Now here starts the main game...
Watch the editorial, not the solution.
Example:
Problem statement is "Write the Program for the addition of 2 numbers," and we understand "Write the Program for subtraction of 2 numbers," so here we read the problem incorrectly.
After watching the problem editorial, identify whether you read the problem the correct way or not.
If you understand or read the problem in the correct way as explained in Point 1.
Then try to solve the problem and take 10 more min "Because right now you are reading and understanding the problem in the correct way."
After watching the editorial, if again you are not able to solve the problem within 10 min, then you go with the "Solution."
But remember, don't write the code by watching the solution.
First, you watch the entire video or article of the particular solution.
Complete the solution video or article and close it.
Take your copy and pen, take some test cases, and try to dry run for better understanding.
After dry run, code it and submit.
Now here starts the main thing that improves your problem-solving skills. "If You Follow"
After all the processes that I explained to you.
Take the pen and paper, not copy, not note down your mistakes that you made during solving the particular problem.
Example:
1st mistake: You did not read the problem statement in the correct way.
2nd mistake: You were not able to implement the concept on your own after watching the video or solution.
Note these points and end "Today Take Complete -> Ab Mja Kro."
Tomorrow again, follow the same process. "But today, you try and focus on those mistakes that you made yesterday so your task is to not repeat these same mistakes again today" and follow the same process.
Obviously, today again, you'll make some mistakes. Write down your mistakes.
Now the question is why I'm focusing on writing down your mistakes. Here are the answers:
After following the approach for 1 week or 10 days.
If you see carefully, your 10-day mistake paper will show a pattern of the mistakes you make repeatedly.
Just take your mistake and start working on that.
Example:
If you see 60% of mistakes in the implementation part, it means you are weak in implementation, so start revisiting your concepts and practicing more problems on implementing algorithms and data structures.
These are the starting rules and steps that I follow. "If you follow, the result will be better, no doubt."