Because anyone worth their salt knows that the superficial hello world example covers the tip of the iceberg. So to say you learned it in two days means you either don’t get that you barely scratched the surface or you dont get what other developers really need when they hire someone with knowledge in a specific framework.
I’m saying that the work they would be doing in two days isn’t the same as solving an actual problem. The way to really learn a language/framework/library is to actually use it in a real project. You run into pitfalls, you get compile errors and have to figure out how to debug in said tech, you find out how extentions to the tech work so you can create your own. Making a Todo Front End isn’t going to cover the vast majority of the stuff I’d expect one to know or experience when you say you “know” a language/framework/library/etc.
You don’t have to actually do a real project. It’s more about doing a task that requires you to create outside the hand holding.
After 15 years of OS and embedded systems development I learned web dev by creating a SaaS for my HOA’s property manager to communicate with tenants. Node, React, MongoDB, docker, iOS and Android apps. Did the project look good? Nope. Did I have to dig into manuals and debug for weeks, yep. But I easily stepped into a new role in an industry I had never worked in because I really learned the tech stack. Actually using the app wasn’t necessary, just that I actually had to create things requiring me to design around the technology I was learning.
Pick a problem in your life and solve it. Doesn’t need to become something you sell or publish or even use after you’re done learning. But the point is to actually use your skills.
Because anyone worth their salt knows that the superficial hello world example covers the tip of the iceberg. So to say you learned it in two days means you either don’t get that you barely scratched the surface or you dont get what other developers really need when they hire someone with knowledge in a specific framework.
Why is it taking you two days to print “hello world”?
You mean print “hello world”; doesn’t work in JavaScript? Well whatever, I bought the book I can put it on my resume right?
Resume:
…
“Goodbye cruel World!” Works fine in JS…
Because React doesn’t have a learning curve, it has a learning wall.
I’m saying that the work they would be doing in two days isn’t the same as solving an actual problem. The way to really learn a language/framework/library is to actually use it in a real project. You run into pitfalls, you get compile errors and have to figure out how to debug in said tech, you find out how extentions to the tech work so you can create your own. Making a Todo Front End isn’t going to cover the vast majority of the stuff I’d expect one to know or experience when you say you “know” a language/framework/library/etc.
If you have to run a real world project before you can consider a tool “learned” none of us would have jobs lol
You don’t have to actually do a real project. It’s more about doing a task that requires you to create outside the hand holding.
After 15 years of OS and embedded systems development I learned web dev by creating a SaaS for my HOA’s property manager to communicate with tenants. Node, React, MongoDB, docker, iOS and Android apps. Did the project look good? Nope. Did I have to dig into manuals and debug for weeks, yep. But I easily stepped into a new role in an industry I had never worked in because I really learned the tech stack. Actually using the app wasn’t necessary, just that I actually had to create things requiring me to design around the technology I was learning.
Pick a problem in your life and solve it. Doesn’t need to become something you sell or publish or even use after you’re done learning. But the point is to actually use your skills.