After finishing more than 200 questions on leetcode. I realize there are so many questions that I have done and I thought I understood later turned out I cannot solve them the second time.
I realized there might be a lot of other people who has similar situation with me. I decided to make some changes on how I do leetcode problems.
- Do not look at answers!
- Treat it like an interview, take 10 min to start basic thoughts.
- If the pseudo code can be generated, check logic and corner cases
- If pseudo code cannot be found, check hints. Sometimes it's an algorithm or data structure should be utilized to solve the problem.
- If no progress in 10 min after hint, watch video explanations and then work it out without looking at answers.
After taking the strategy above I can feel the progress I made and also gain more confidence. This leads me to share my thoughts during solving the problems, I think these might become a hint for whoever doing the same questions.
So I started the repo following the same pattern of Neetcode (The author is so good!).
The repo started about 2 weeks ago and I realize it might be more helpful if I can provide some video explanations. But this is an area I have never touched. The idea of video meeting with whoever interested rises.
I started to give video meeting link in my Flatiron cohorts. At first two sessions I gave out more easy questions cause I don't want to scare whoever didn't start leetcode. But on the contrast, the speed of my explanation of my thoughts are still fast that makes my classmates not interested in solving this.
Until recently I found one classmate who can follow my thoughts. That we solved a hard level leetcode question in two hours gave me lots of boosts. Even though the second day he told me about the same issue that I went too fast.
I will keep sharing the leetcode questions I have worked on and try to start video explanation in about two weeks. Have to remind me that I shall try to explain questions like explaining to someone never touched programming.
Feel free to check my GitHub and the repo. All comments welcomed.
Top comments (0)