An education consultancy focused on researching, designing, building, and testing cutting-edge curriculum, running bold experiments to innovate learning.
HTML
I considered it to be pretty self explanatory and didn't dedicated anytime here
This is scary.
And then seeing all that React!
We tutor boot camp grads all the time, and they get rushed through HTML and CSS - and JS - and straight to Bootstrap and React. Then if they don't have "hooks" they can't make anything / and they have very distorted models for how everything works.
Consider just starting to build things: Maybe a "business-card" style website to start. MDN HTML and CSS references. This way, you are making something practical right out of the gate. You can also get help in the CSS Discord.
If you learn in order of necessity - you will loose a lot less time. The less code to get the goal the better right? No one has ever had the goal of "having a website" or "learning web pack." The goal is usually something else - and those are just tools to get there. If you set goals like "learn about coding" then that's what you'll get. Consider setting a measurable goals - with timelines.
This is great advice. Everything ends up as HTML, CSS and JS in a browser, so treating two of those three things as unimportant (ie, spending more time on Webpack than HTML) is not a great strategy, imo.
This is scary.
And then seeing all that React!
We tutor boot camp grads all the time, and they get rushed through HTML and CSS - and JS - and straight to Bootstrap and React. Then if they don't have "hooks" they can't make anything / and they have very distorted models for how everything works.
Consider just starting to build things: Maybe a "business-card" style website to start. MDN HTML and CSS references. This way, you are making something practical right out of the gate. You can also get help in the CSS Discord.
If you learn in order of necessity - you will loose a lot less time. The less code to get the goal the better right? No one has ever had the goal of "having a website" or "learning web pack." The goal is usually something else - and those are just tools to get there. If you set goals like "learn about coding" then that's what you'll get. Consider setting a measurable goals - with timelines.
Consider these books as a guide:
Good call, I will definitely spend some time to cover the HTML basics :) Thanks for the pointers!
This is great advice. Everything ends up as HTML, CSS and JS in a browser, so treating two of those three things as unimportant (ie, spending more time on Webpack than HTML) is not a great strategy, imo.
Yeah, I totally agree on building a solid foundation on html, I was trying to wing it with CSS and ended up wasting a lot of time.
I added something in the post to call out this point