One of the things that helps me is that I'm usually looking at some tutorial 'after' I have a project that I need to get going on right away, so the tutorial tends to be JIT. As soon as I get a handle on some key point I need to be able to implement, I'm off and running on my project applying what I've learned right away. If I get stuck then I'm back to a tutorial again, but most often don't need it anymore, but instead will start working with reference materials for the language because tutorials take too long and will often become painful to have to endure. I'll often use stack exchange to get specific solutions to problems I have yet to understand how to solve with the new tools and or language.
One thing i learned in development is that there are many solutions to one problem. As ive gotten more experienced i always notice small things that an instructor does in a tutorial that i personally would not do or seem counter intuitive to me. Nonetheless using tutorials as starting points are great but after a while you should get your own groove on things.
I gave up on learning code (got too absorbed into what I already do, design & motion graphics), but I still watch a lot of Stefan’s videos. He’s excellent at breaking things down. 🤙🏻
When I go to a tutorial, it's usually to find out exactly how a function works or gets used. I go in knowing what I need to know already. So I do a lot of skipping while watching a tutorial. I only bother with tutorials if stackoverflow doesn't have an answer. I'm never going to find a tutorial that explains how to code the project I'm currently developing.
I am currently in tutorial hell but not that deep....I teached myself how to implement CRUD functionality using the MERN Stack and some core understanding of front and backend development. Now i want to get out and build my personal portfolio page.
A mistake I made when I was learning was doing tutorials that were way too advanced for a beginner. Focus on simple tutorials. I'd probably advise to just learn html and JavaScript first. You can learn the CSS later, just learn dom manipulation and interacting with a web service using JavaScript. Then I'd learn to make a simple restful service that can deliver the basic crud operations and that stores data in a database. Do tutorials to learn those most basic fundamental things about web dev. From there, you can now make calls to your own API that YOU made. Worry about styling later. I'm at my first job and the 1-2 months I spent learning about styling with CSS and making nice looking responsive pages with media queries did not help me get this job at all.
True I also had that the mindset that I would not move to backend until I perfect my knowledge in frontend.... after I started working I realized how stupid that has been....
@avfr I work remote. I do full stack work; some front end and some backend. Even on the front end, they already have a repository of styled components. I did study data structures and algorithms. Do 1 problem a day for 30 min, if you can't solve it within 30 minutes, look up the answer and spend another 30 minutes trying to understand the solution. This is more productive than wasting 2 hours trying to come up with a solution if at all. Eventually you'll be able to solve similar problems on your own.
@avfr I don't want to give details as it could reveal my identity. But it's for a mid-large sized company. We maintain the website they use to sell their products and services.
Is it good after a long break to getting into project rythm by following some step by step tutoriak project to getting back in taste or making own projects because after long break starting new project without feeling of project creation ?
I think that is not tutorial hell, that is tutorial stuck. Tutorial hell is if you fallowing any tutorial, and in half of that, it not working any bug, and youtuber dont care and dont explain it. and After that U see in comments many ppl ask for help and solution, that is for me tutorial hell. What you?
One of the things that helps me is that I'm usually looking at some tutorial 'after' I have a project that I need to get going on right away, so the tutorial tends to be JIT. As soon as I get a handle on some key point I need to be able to implement, I'm off and running on my project applying what I've learned right away. If I get stuck then I'm back to a tutorial again, but most often don't need it anymore, but instead will start working with reference materials for the language because tutorials take too long and will often become painful to have to endure. I'll often use stack exchange to get specific solutions to problems I have yet to understand how to solve with the new tools and or language.
That's pretty much how I go about it : Only look for a tutorial after encountering the problem I need to solve to make my project work. learn as I go.
Uncle Stef back at it again with another video. Thanks Stef! :)
You bet!
It's almost like you're saying that watching porn all the time isn't going to make me a spectacular lover.
One thing i learned in development is that there are many solutions to one problem. As ive gotten more experienced i always notice small things that an instructor does in a tutorial that i personally would not do or seem counter intuitive to me. Nonetheless using tutorials as starting points are great but after a while you should get your own groove on things.
I gave up on learning code (got too absorbed into what I already do, design & motion graphics), but I still watch a lot of Stefan’s videos. He’s excellent at breaking things down. 🤙🏻
Uncle Stef,
How to learn best practices when learning alone? (When building projects by myself)
When I go to a tutorial, it's usually to find out exactly how a function works or gets used. I go in knowing what I need to know already. So I do a lot of skipping while watching a tutorial. I only bother with tutorials if stackoverflow doesn't have an answer.
I'm never going to find a tutorial that explains how to code the project I'm currently developing.
I am currently in tutorial hell but not that deep....I teached myself how to implement CRUD functionality using the MERN Stack and some core understanding of front and backend development. Now i want to get out and build my personal portfolio page.
a tutorial on how to get out of tutorial hell, perfect.
Not everything learned can be tought.
A mistake I made when I was learning was doing tutorials that were way too advanced for a beginner. Focus on simple tutorials. I'd probably advise to just learn html and JavaScript first. You can learn the CSS later, just learn dom manipulation and interacting with a web service using JavaScript. Then I'd learn to make a simple restful service that can deliver the basic crud operations and that stores data in a database. Do tutorials to learn those most basic fundamental things about web dev. From there, you can now make calls to your own API that YOU made. Worry about styling later. I'm at my first job and the 1-2 months I spent learning about styling with CSS and making nice looking responsive pages with media queries did not help me get this job at all.
True I also had that the mindset that I would not move to backend until I perfect my knowledge in frontend.... after I started working I realized how stupid that has been....
@avfr I work remote. I do full stack work; some front end and some backend. Even on the front end, they already have a repository of styled components. I did study data structures and algorithms. Do 1 problem a day for 30 min, if you can't solve it within 30 minutes, look up the answer and spend another 30 minutes trying to understand the solution. This is more productive than wasting 2 hours trying to come up with a solution if at all. Eventually you'll be able to solve similar problems on your own.
@avfr I don't want to give details as it could reveal my identity. But it's for a mid-large sized company. We maintain the website they use to sell their products and services.
I need advice on how to escape "how to escape tutorial hell" tutorial hell ?
Start building something from scratch. Start with something simple.
@@StefanMischook I highly suspect you missed my point. There were too many tutorials. Now, there are too many "how to escape tutorials" videos.
@@GeorgeTsiros Ahh ... got it. The real problem is we have too many fake experts 'teaching'.
Is it good after a long break to getting into project rythm by following some step by step tutoriak project to getting back in taste or making own projects because after long break starting new project without feeling of project creation ?
Which hell is worse: tutorial hell or dependency hell?
Ahhh .... long term: dependency.
Maybe that's why I haven't learned JavaScript🤔
make me fall sleep this video
Good night!
A friend of mine has been in tutorial hell since high school, except he calls it "Chow Gar"
LOL!
I wonder what his name is ... Bruce?
Minimalistic css on your head still looking okay
Is this a reference to Kyle's hair from webdevsimplified?
I think that is not tutorial hell, that is tutorial stuck. Tutorial hell is if you fallowing any tutorial, and in half of that, it not working any bug, and youtuber dont care and dont explain it. and After that U see in comments many ppl ask for help and solution, that is for me tutorial hell. What you?
I was put into this by a boss I had.