I made 21 list items about the way you should study coding

swishyfishie2 profile image Swishyfishie ・3 min read

The purpose of this article is to break down the pros and cons on learning types and at the end I'll tell you the method I used to learn JavaScript quickly and correctly!

Think outside the box written on a blackboard

If you don’t know already, we all learn differently. We’re all a mixture between ratios of “Visual”, “Reading/Writing” “Auditory” and “Kinesthetic” styles.

I’ve came up with 3 categories related to coding:

Reading - Listening/Watching - Practical Coding



  1. Mental stimulation
  2. Memory improvement
  3. You can easily review/revisit topic
  4. Easy to make notes with highlighters


  1. It might question your ability to focus due to the low attention span we all have nowadays
  2. Can lead to eyestrain faster if you read in a bad light or on a P.C. (turn that blue light filter on!)
  3. You may get tired easily as reading technical documentation is really exhausting for the brain



  1. Your brain can focus more on concepts and theory if you get a good tutor that has an engaging style of teaching
  2. You can formulate questions much easier when listening/watching
  3. Opportunity to ask question if you attend an online workshop or a live class


  1. Information may not be retained if you are not actively listening/participating
  2. You may get a bad tutor, a boring one or one that you don’t like

Practical (coding-along/building projects)


  1. YOU ACTUALLY CODE! This is the most important part of your journey. TOUCH THAT KEYBOARD!

  2. This style is an amazing way of learning because you get to see how others think, how they approach problems and how real people code.


  1. The tutorial you’re following might go through concepts that are unfamiliar with you.

  2. Due to physical resources (a small laptop for example), it may be hard to use multiple windows at the same time and have good visibility on what actually happens on the video.

If you're studying JavaScript I have a infallible method for it.

The pattern is like this:

  1. Open up your freeCodeCamp and do your tasks there.

  2. Read every piece of information and if it seems too easy to do, don't hesitate and do it, otherwise you’ll be trapped between “it’s too easy/it’s too hard” and you won’t do anything.

  3. Go to youtube or your prefered Udemy tutorial and click play. Try to resize the windows so that you’ll comfortably see what happens on the video and what happens in your code editor.

  4. Pause frequently and go to MDN as much as possible. A succesfull code along is that when you know most (if not, all!) of the concepts presented by the tutor.

  5. Reward yourself.

Remember that just because you’re doing it by yourself in the comfort of your own home, it doesn’t mean that you shouldn’t put a massive effort into it. Learning to code is hard work and you should expect things to be difficult BUT also enjoyable.
If it's too easy then you're not learning.

Happy coding and spread love!

Posted on by:

swishyfishie2 profile



Full-stack developer. I like rubies and javascripties.


markdown guide

I have a background in teaching German as a foreign language and I found there a certain pattern in which to structure classes. Since that pattern applies to learning in general, I would like share it with you, to add to the conversation.

When talking about learning, I want to differentiate between
a. learning systematically and
b. learning unsystematically.

The first one is choosing a topic and then setting out to learn that topic and the latter is doing a task and learn as you go, without control of what you will learn. As an example from learning a foreign language, the first way is picking a grammar topic and then sitting down to learn that, the second way is going to get a haircut in a country/region where the language is spoken. You certainly will learn something, but it is unpredictable what you will learn.
Both are valid ways to learn, but you should be aware of their existence and choose consciously.

A class/learning session to learn something systematically is ideally structured in the following way:

1 Introduction: Get an overview of the topic and see what you might know already.

When self teaching coding, this would be some theoretical articles or high level view presentations.

2 Presentation: Take a closer look at the problem/phenomenon you want to learn in that session. Read, talk about the details and facts, rules, etc.

This is getting into the nitty gritty. Rwad documentation and highly detailed articles.

3 Verify. Check the understanding. Answer questions, if in doubt, go to 2.

When learning alone, this one is tricky. I recommend that you talk about it with someone, write a blog or make a video. Try to explain what you learned. See Feynman.

4 Guided practice. Follow guided exercises. There is no need for creativity here, it is supposed to be more of a drill at this stage.

This is where you code along and follow tutorials. You'll use the learned information but in a guided way.

5 Transfer. Apply what was learned in a different context on your own.

Finally, go do something on your own. Use what you learned in a context that is relevant to you. This is the hardest and most important step, don't skip it before moving on to the next.