Don't get me wrong, I love tutorials. I can follow a 57 hours tutorial without any issues.
After a month of intense learning (around 50 to 80 hours per week), I started applying for jobs while branding myself as a pro developer (like the courses I was following stated).
First job interview, I wasn't able to do a simple HTML table by myself and didn't understand jack shit about JQuery. And that did hit my confidence really hard.
What I realized quickly is that I was just riding with training wheels. I never practiced on my own or tried to redo the exercises by myself.
So yes, tutorials are awesome, but they're here to teach you different concepts around a specific example. They can't exactly spend 27 hours saying "google that and we'll keep moving forward from there.
I got into the habit of not publishing my code online. I could do things on my own, but I was still feeling like a NOOB.
Having a portfolio was far from happening as well. If my code was so bad, why would I show my shitty designs on top of that?
There's a whole Elite thing going on around the IT field, especially when we get around programming and more generally CS.
To be honest, this should not throw you off.
It will still be scary to publish your code and what you did online, but same old same old, the people who will go on and on about how much you suck are usually not the one who will get you a job, get you an interview or pay your bills.
And to have those things, you have to show something to recruiters and other reviewers. I did a technical interview where we had to a simple SPA, I told the persons that I didn't know how to those things and sent them my code and the application.
I had really valuable feedback from the lead developer and the tech lead.
React, Angular and Vue are not going anywhere any time soon, we all agree on that one.
Basically, frameworks are stuff that produces code behind the scenes to make some cool things happen on the screen (yes, it's not technically accurate, but you get the point).
To get my point even more across, we can even say that it's not that much different than copying the cool piece of jQuery and having something that works on the spot (almost).
The issue with that is that you won't really understand the internals of what you're working with.
Also, you won't overload your applications or websites with unnecessary things because you had absolutely no idea of what you were doing.
Don't do that. Getting a job in the industry is cool and everything, but that doesn't mean that you should say yes to things that are just bonkers.
I'm guilty of that.
I was so cocky that I spent 45min bashing Angular (which I didn't touch even once back when I did this interview), and then asked for 3 days of remote work even during my trial. I didn't get the job obviously.
Fast forward a few years, and here I am applying for a frontend position.
And nope, this is not a joke.
Just say no to those types of things, and stay honest and humble about what you can or can't do. People who are more experienced than you will assess your level and probably give you some feedback about what you should work on if you ask them nicely.
Having a job for the sake of having a job is not worth it. Best case you'll end up depressed after a while, worst case you'll just burn yourself and will end up hating what you spent so much time learning.
Now tell me, what screwed you over when you started?
If you interviewed some people, do you have any crazy stories?