I really love computer science, coding and mostly all the amazing things you can do with this knowledge, i feel i finally landed in my world.

I’m doing a Javascript course now and while it is really engaging to learn about how a language like that works and how to build with it, i’m getting quite tired and frustrated…

Now, i’d say i am quite meticulous when studying and i use some studying techniques to really integrate what i’m learning, but that means that 1h or even less lesson can take me all the time i have to study in a day to be understood, noted down and then repeated over the following days…

There are a lot of quite complicated concepts to understand and memorize, and, as i’m also working, sometimes it gets quite tiring.

I feel like there’s this huge amount of never ending work and concepts before i can actually start do something cool with the knowledge i have, and i really want to start doing something cool.

I re-started to study after many years so i’d say it’s also because of that if i’m not really used to it and i can’t process much informations at the time.

How can you get better into gaining knowledge? how can you prevent getting fatigued?

  • @OneCardboardBox
    1•1 year ago

    When I learn new programming frameworks/languages/etc, I do the following:

    • Read: I learn about the thing by looking up documentation and online posts
    • Tutorial: I then find a guide that walks me through doing something for real.
    • Mixup: Halfway through the tutorial, if I think I’m starting to understand how it works, I stop following it. I practice adding something new that the tutorial doesn’t mention, or I try and do it in a different way.

    The most important part for me is the mixup. When I break away from a tutorial, I usually run into unexpected problems. Things don’t compile or don’t work as expected. This is where the real learning comes from, because now I’m learning how to solve problems for this language/framework. My problem with many tutorials is that they tell you “what” to do but not “why” it’s done that way. Well, when I break things unexpectedly and have to solve it myself, that’s when I learn the why.