For me "tutorial hell" was going through a tutorial, step-by-step, and then just moving on to the next tutorial. My learning style dictates that I apply my knowledge first hand. Tutorial hell is going to look a little different for each person based on their learning styles. Here is my current strategy:
1) Run through a tutorial for a whole brand new technology (I don't always do this, for instance for the hackathon that Dev.to is doing with web monetization I just jumped right into Vue.js. I had seen someone coding with it on Twitch and I was intrigued. I just looked up documents for Vue.js from their site and other blogs).
2) Take the knowledge I have and apply it to a project to secure those skills in my brain. To run back to step 1, if I feel like I know the direction I am heading and I think I can tread a bit on my own, I may just dive right in.
The #1 most important/critical/useful thing you can do as a learner (a developer is just a life long learner after all) is figuring out how you learn the best. What makes you retain the knowledge. What gets you from 0-100 the fastest. It can be challenging. For me, going through American public school from the late '90s to the late '00s, there was no learning style. Learning happened one way and one way only.
Maybe you learn best with tutorials, but you need to know when to break away and build something. That's "tutorial hell" part 2. You can feel stuck going from tutorial to tutorial. You never build anything yourself. You never actually make. Making is a big part of development.
As one last bit, I have been rambling, don't stress too much. Take time to evaluate how you best learn. Join different communities and find peers that can help you succeed. Work hard, but don't overburden yourself.
For me "tutorial hell" was going through a tutorial, step-by-step, and then just moving on to the next tutorial. My learning style dictates that I apply my knowledge first hand. Tutorial hell is going to look a little different for each person based on their learning styles. Here is my current strategy:
1) Run through a tutorial for a whole brand new technology (I don't always do this, for instance for the hackathon that Dev.to is doing with web monetization I just jumped right into Vue.js. I had seen someone coding with it on Twitch and I was intrigued. I just looked up documents for Vue.js from their site and other blogs).
2) Take the knowledge I have and apply it to a project to secure those skills in my brain. To run back to step 1, if I feel like I know the direction I am heading and I think I can tread a bit on my own, I may just dive right in.
The #1 most important/critical/useful thing you can do as a learner (a developer is just a life long learner after all) is figuring out how you learn the best. What makes you retain the knowledge. What gets you from 0-100 the fastest. It can be challenging. For me, going through American public school from the late '90s to the late '00s, there was no learning style. Learning happened one way and one way only.
Maybe you learn best with tutorials, but you need to know when to break away and build something. That's "tutorial hell" part 2. You can feel stuck going from tutorial to tutorial. You never build anything yourself. You never actually make. Making is a big part of development.
As one last bit, I have been rambling, don't stress too much. Take time to evaluate how you best learn. Join different communities and find peers that can help you succeed. Work hard, but don't overburden yourself.
Thank You!!!