I think it's really about interleaving 'doing' and 'reading'.
I used to be more of a reading person, but I find that I am a bit faster to learn now if I lean more towards doing.
First I try to understand if something WORTH learning. For example, is R worth learning? Yes. Is React worth learning (for me)? Not sure yet but I'm keeping my eye on it.
Then I try to first get a "hello world" running without too much understanding. This can actually be the hardest part... building software is sometimes harder than understanding the ideas :) And once I have hit a wall playing with things, then I need to go back and read some more to figure out the concepts.
Once you've played with enough software, you can get surprisingly far just by doing things, and actually learn the concepts. Other times you can get stuck and need to go back and do some research.
The doing gives context for the reading phase. Without it, there is no place for the concepts to attach in the graph of knowledge. It is similar to skimming a book to get structure, knowing the destinations allows the journey to make more sense.
I used to be more of a reading person, but I find that I am a bit faster to learn now if I lean more towards doing.
First I try to understand if something WORTH learning. For example, is R worth learning? Yes. Is React worth learning (for me)? Not sure yet but I'm keeping my eye on it.
Then I try to first get a "hello world" running without too much understanding. This can actually be the hardest part... building software is sometimes harder than understanding the ideas :) And once I have hit a wall playing with things, then I need to go back and read some more to figure out the concepts.
Once you've played with enough software, you can get surprisingly far just by doing things, and actually learn the concepts. Other times you can get stuck and need to go back and do some research.