Framework tutorials will always only cover the basics to get you to the point where you feel comfortable starting a project with it. Your experience is one I'm sure many have experienced, myself included.
For me, picking the right tutorial to teach me something very specific ended up being far more valuable all in all. The rest is always picked up through trying to solve a particular problem you've never encountered before. That never really changes as there's always something 'new' to tackle but the frequency that occurs depends on tasks at work / side projects and in turn the faster you learn.
I could spend all my spare time watching tutorials but if I can't apply it to what I'm doing right now or it's not something I'm genuinely curious about, I pass on it.
Experience with things like Webpack and config in general also will come naturally over time, boilerplates are starting points. On your own project I'd be very surprised if you don't need to amend them at some point, picking up things along the way has been far more useful than doing a Webpack tutorial (for example) :)
Thanks, I fully agree to that. It just took a while until I realized that it's a lot easier to learn along the way, as problems occur.
I'm pretty sure that I will have to get some Webpack experience, but as long as I don't get to the point where I actually have to do it, I'm putting that aside and focus on things that are more important at the moment.
Like you said, when you get to a point where you want to solve something specific, doing a tutorial isn't that bad. You learn about a specific thing and since you instantly use what you've learned, chances are higher that it'll also stay in your head :)
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.
Framework tutorials will always only cover the basics to get you to the point where you feel comfortable starting a project with it. Your experience is one I'm sure many have experienced, myself included.
For me, picking the right tutorial to teach me something very specific ended up being far more valuable all in all. The rest is always picked up through trying to solve a particular problem you've never encountered before. That never really changes as there's always something 'new' to tackle but the frequency that occurs depends on tasks at work / side projects and in turn the faster you learn.
I could spend all my spare time watching tutorials but if I can't apply it to what I'm doing right now or it's not something I'm genuinely curious about, I pass on it.
Experience with things like Webpack and config in general also will come naturally over time, boilerplates are starting points. On your own project I'd be very surprised if you don't need to amend them at some point, picking up things along the way has been far more useful than doing a Webpack tutorial (for example) :)
Thanks, I fully agree to that. It just took a while until I realized that it's a lot easier to learn along the way, as problems occur.
I'm pretty sure that I will have to get some Webpack experience, but as long as I don't get to the point where I actually have to do it, I'm putting that aside and focus on things that are more important at the moment.
Like you said, when you get to a point where you want to solve something specific, doing a tutorial isn't that bad. You learn about a specific thing and since you instantly use what you've learned, chances are higher that it'll also stay in your head :)