I always see questions like that how many time is need to learn some new technology.
The truth is you can't learn a new language/framework in 5 h...
For further actions, you may consider blocking this person and/or reporting abuse
It seems so obvious to start with the documentation but that is what I NEVER seem to do and I go straight to tutorials and courses haha. Great article, I've started learning Vue.js this week and this article has made me realise where I'm going wrong. I'll start with the documentation first and implement what I learn. Thanks.
I'm happy that the article did help you if need some help, you can send me a message 🙏
I came from the java world and you know the oracle docs. Then some youtube fellows made interest in other language and technologies. Youtube's persuasive design made me stick in youtube and bhoa. I turned into another tutorial follow. Instead of spending few minutes in docs, i wasted hours into videos. Modern docs are quite readable though. Like 70% docs, 25% tutorial, 5% fun. and all mixed together.
Hey man, i am trying to learn java too, but the official Docs sucks. Suggest some resource to learn it. BTW I'm from C/C++ background 😬.
Like with most languages (including programming), one can engage the learning process using a SCRUM-like approach - iteratively, functionally, and bootstrapping. If you become top-heavy with reading documentation-tutorials or diving prematurely into extended example code snippets, you will elongate your learning process or even fail to meet your timeline goals for learning. This is akin to top-down and bottom-up approaches respectively. They are not an efficient means of obtaining a working knowledge of a subject matter.
If you are going to engage in a code snippet, use documentation to learn the component parts of it before you improvise it. Do not stick for too long a period of time with that improvisation of the code snippet because it may outlive its usefulness as the best way to accomplish your algorithmic purpose. Jump to other approaches within the language and/or others' approaches. You will always produce code that will be more efficient, correct, and elegant than others' or worst than others' respectively. The learning process never ends and then once you start reaching star status with one, it dies a death, being replaced with a better language. That is what it means to be homo-sapien in a homo-sapien society.
Additionally, you may have considered giving a very brief intro or description of React (i.e., a 5-year-old javascript library for interface development, View part of MVC, VDOM binding, with scalable fast component-based server-side rendering).
I also started by reading the official docs, but for the rest I wasn't as disciplined as you, didn't practice systematically, which is bad if you want to learn something really well. But reading the official docs as a first step is a winner.
The best way to learn something new as always is to just build projects. It's a no brainer but still many get stuck just following a tutorial blindly. Once you make that break away and start doing what you want to do it is game changing the ideas just flow when you see how capable you are.
Thank you so much for all of this advices and tips. It's a huge article. Can you give us some projects to clone it and increase our skills?
Sure, I will share my repository with the projects
Oops no, I was joined bootcamp first . .
You aren't being clear how much learning is learnt. Cutting point? Suitable for junior positions?
I've been using React for about 5 years, and I'm still learning it. It has evolved so much, so quickly, that I don't think I'll stop learning it any time soon.