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).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
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).