This is absolutely true. If there is one thing you absolutely have to learn, it is the ability to read (and write) documentation. Google, YouTube, or Stack Overflow will not always be there to hold your hand. You have to learn how to learn by yourself through documentation.
There will be times when the terminology used by the documentation is too advanced (such as the case with some topics in MDN). In those times, it is essential to slow down and learn the fundamentals first before diving deep into those advanced topics. However, there may be other times when it is not exactly necessary to bother too much with the terminology. It is up to you to judge what information you will need from the documentation. And that is the true skill of learning through documentation: knowing and getting what you need from the documentation.
In every documentation, especially with JavaScript frameworks, the best place to start is always the Getting Started section. From there, you can branch out and discover what the API can offer you.
And one last thing: you are not supposed to memorize everything about a certain API. That is why we have documentation for it in the first place. Memorizing the features of an API naturally comes with experience. Don't force it to stick in your brain. Just go back to the documentation for the information you need when you need it. That is a more effective way of learning.
This is absolutely true. If there is one thing you absolutely have to learn, it is the ability to read (and write) documentation. Google, YouTube, or Stack Overflow will not always be there to hold your hand. You have to learn how to learn by yourself through documentation.
There will be times when the terminology used by the documentation is too advanced (such as the case with some topics in MDN). In those times, it is essential to slow down and learn the fundamentals first before diving deep into those advanced topics. However, there may be other times when it is not exactly necessary to bother too much with the terminology. It is up to you to judge what information you will need from the documentation. And that is the true skill of learning through documentation: knowing and getting what you need from the documentation.
In every documentation, especially with JavaScript frameworks, the best place to start is always the Getting Started section. From there, you can branch out and discover what the API can offer you.
And one last thing: you are not supposed to memorize everything about a certain API. That is why we have documentation for it in the first place. Memorizing the features of an API naturally comes with experience. Don't force it to stick in your brain. Just go back to the documentation for the information you need when you need it. That is a more effective way of learning.
Don't memorize. Internalize.
Thanks a lot Some Dood. Really appreciate the advice!