You have pointed some of the biggest issues with the development courses nowdays, and the ecosystem as a whole.
I (try) to mentor junior web developers, and the problem I face is not the lack of resources for them, rather the opposite, which of them are good and in what order.
However, there really should be better ways of parsing this stuff for beginners. Give us the tools to strip away some of the abstraction
There are ways to peal off the abstractions, but is a longer, harder path of learning, with a late ReturnOfInvestment, one of them is doing a 3-4yrs CS faculty.
All of the courses, nanodegrees and codecamps I saw will skip the basics, what JS is and how does it work, how a Computer works, and entire chapters like security and performance. Why? I guess because they want you to be productive as soon as possible.
You will loose many hours because you skip the basics? Sure, but meanwhile you already shipped a few websites with webpack and other frameworks.
That is why I have 2 main paths I help the juniors "walk":
You want to have a career, you are in this on the long run, and can spare a few months of training?
I will say to learn CS and the tools first and in parallel with the main language. Learn what is a pointer, wha is the job of the OS, a process and a port. Learn what ECMAScript is before JS, learn a static typed language first before entering the Dynamic programming mess. Learn the difference between an array, list, object before doing `map["ss"]" in JS.
This were random examples, I recommend what to learn depending on the position and skills the dev has.
2 . You want to get a job ASAP and "make websites"? Learn a small amount of JS/CSS and React and go for it. We can come back to the basics as you go.
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.
You have pointed some of the biggest issues with the development courses nowdays, and the ecosystem as a whole.
I (try) to mentor junior web developers, and the problem I face is not the lack of resources for them, rather the opposite, which of them are good and in what order.
There are ways to peal off the abstractions, but is a longer, harder path of learning, with a late ReturnOfInvestment, one of them is doing a 3-4yrs CS faculty.
All of the courses, nanodegrees and codecamps I saw will skip the basics, what JS is and how does it work, how a Computer works, and entire chapters like security and performance. Why? I guess because they want you to be productive as soon as possible.
You will loose many hours because you skip the basics? Sure, but meanwhile you already shipped a few websites with webpack and other frameworks.
That is why I have 2 main paths I help the juniors "walk":
I will say to learn CS and the tools first and in parallel with the main language. Learn what is a pointer, wha is the job of the OS, a process and a port. Learn what ECMAScript is before JS, learn a static typed language first before entering the Dynamic programming mess. Learn the difference between an array, list, object before doing `map["ss"]" in JS.
This were random examples, I recommend what to learn depending on the position and skills the dev has.
2 . You want to get a job ASAP and "make websites"? Learn a small amount of JS/CSS and React and go for it. We can come back to the basics as you go.