Coding is like riding a bike.
You can’t really learn how to ride a bike by watching how to ride a bike videos, reading how to ride a bike books, following how to ride a bike online tutorials, enrolling in bike riding online courses, listening to bike riding blog podcasts. If you want to learn how to code, you must actually be coding.
I think you’ll get more learning done by reading a few pages, then opening your browser’s console, or your codepen editor and trying out what you just read. Type in the code (no copy-pasting!). Change values, change the order, play what if scenarios, introduce intentional mistakes, typos, and see what kind of error messages you get. Google the commands/function names and see what other related functions are there. Try some of them out on your own, on how to use it. See if you can figure it out and be able to write your own line of code.
When done — read the next few pages, then repeat cycle again. It will be real painfully slow at the beginning… but over time you’ll learn much better, and what you learn will stick to your brain.
There should be more hands-on coding time than reading/watching time.
But reading a whole chapter or book, or watching an online video from start to finish without even opening up your code editor and trying to write your own code? That will not be productive at all. By the time you finished the course or the video, you’ll be asking yourself “What did I learn? I still can’t write code of my own.”
Also… DISCIPLINE – A few minutes of reading, and several minutes to half hour or hour of daily coding will be more productive than binge reading/coding that lasts for several hours, every now and then. Your brain will be fried and you won’t absorb everything. Your brain needs time to rest to process what you just learned. Doing marathon 8 hour learning sessions is like cramming – you think you understand and know it, but a few days later… you forget everything.
YMMV – your mileage may vary. If your current learning method doesn’t work, try this.
