Review schedule for long term benefits

I recently attempted a LeetCode Contest but I could not solve a problem. The reason I could not solve the problem is that even though I knew it was similar to a problem I had worked on previously, I did not know how to solve that previous problem.

Algorithmic problems are based on pattern recognition but that pattern recognition isn’t helpful if too much time has passed.

To increase my retention I am using this schedule https://www.quora.com/Whats-the-best-spaced-repetition-schedule. It is the Fibonacci numbers. I am using Gmail’s ability to snooze emails to the future to practice algorithmic problems that are helpful in solving many other problems.

Lynda & Team Tree House

I started learning from these awesome resources. They were free because of my local library 🙂

With Lynda (now called LinkedIn Learning) I only took one course on Object Oriented Design and it was very clear and concise.

I am impressed with Team Tree House because it is interactive like Codecademy and in depth as well. They also teach how to use documentation and have small projects along the way.

Check out your local library and see if you can get these resources for free 🙂

 

Top web development boot camp is now free

App Academy’s Ruby on Rails and React Boot Camp is now free! Here is a news article and here is the link to the free boot camp

Amazing article on becoming a rock star developer

Focus and Deep Work : This great article summarizes Cal Newport’s Deep Work lessons as well as teaches how to apply the Pomodoro Technique to level up one’s skills

My current goal setting system

In the past I have tried many ways of keeping track of my goals including writing them down daily,  using a mind map, Post It Notes, even trying out index cards and recording them and listening to them while exercising.

I don’t think there is a best system because I think the ideal goal system for each person will have to be built via try, fail, learn, and improve. Also what works today might not be optimal in the future.

My current system is to every day email myself my goals and to dos. To make them stick and to gain more commitment I paraphrase every goal and I also add due dates. I also add easy to dos to feel good and to take steps towards my goals.

I think the paraphrasing is beneficial to me because if I just read the goals I don’t really have to think about them, but if I try to force myself to write them by hand every day that would be too much work and I would quit after a few days. I feel like paraphrasing is a nice balance between commitment, work, and usefulness 🙂

Design Patterns Resources

Here are a few links that have helped me gain exposure to design patterns:

• Design Patterns Video Tutorial
• Design Patterns Tutorial
• Java Design Patterns
• Head First Design Patterns

I recently started learning from kudvenkat and he is a great teacher who provides clear, simple, and detailed explanations and examples. I am sure his series Design Patterns Videos are great as well.

Random Motivational Tips

Here are a few tips that have helped me on my journey

• Remember my purpose and long-term goal(s).
• Forget about my long-term purpose and goal(s). Instead focus on the next step, or even just doing a few seconds of the next step.
• Write, read, and paraphrase my to dos and goals regularly. I currently email myself my goals and to dos every day.
• When I feel overwhelmed thinking that there is too much to learn, that technology moves fast, I remind myself that is a great thing. The opposite is an industry or a job that never changes, which is mind-numbing and boring. Also new technology is constantly being created to solve problems better, faster, more easily (in theory 🙂
• When I watch an educational video and think to myself, “How can she/he possibly know all of this?” I remind myself, “It is great that she/he knows this and is teaching me. I can cut down on the learning curve by learning from this teacher.”

 

System Design Resources

Here are some great resources for learning System Design:

• System Design Primer
• Grokking the System Design Interview (PAID)
• Tushar Roy
• Hired In Tech
• Interview Bit
• High Scalability
• System design interview

To learn these I recommend: Learning by repetition and paraphrasing

Learning by repetition and paraphrasing

I have been learning material by using a combination of repetition and my variation of The Feynman Technique.

My strategy is to repeat the material in chunks, i.e. section 1, then section 1 and 2, then sections 1 through 3, sections 1 through 4, etc.

I try to paraphrase every sentence. Sometimes it’s I just reverse the sentences, sometimes I change them into a question and answer, and sometimes I just use synonyms for a word or for multiple words in the sentence.

I think this has been working for me because of the sheer number of repetitions, but also because I am actively engaging with the material, and I am jamming the information into my working memory. Furthermore, I am exposing myself to the material in many different ways because I probably paraphrase things slight differently each time.

I think if I get comfortable with the earlier sections, I might start reviewing from the later sections. For instance, if there are 10 sections, I might review section 10, then section 9 through 10, then 8 through 10, etc.

I think I can certain material into long term memory by using flash card software. Also for things that just have to be memorized, I can create pictures, patterns, stories, rhymes, or use memory techniques such as The Link Method.

Forget About Setting Goals. Focus on This Instead.

Here’s a great article on how setting goals can actually be counterproductive and demotivating: Forget About Setting Goals. Focus on This Instead.

My personal philosophy is to focus on the process by setting up a system and simply following it. I try to make my system consist of fun and right actions, so that way I can happily achieve towards my goals instead of achieving to be happy. I try to trust the process and see what happens, which lines up nicely with James Clear’s article 🙂