The most important thing I’ve learned as a developer is that it’s really easy to get stuck in tutorial hell. You get comfortable with the fact that there’s somebody out there willing to teach you, write guides, roadmaps…etc, and then one day you realize you have the information but you don’t know what to do with that information. You are given a project, and realize that you have no idea where to start. Boom. Tutorial hell!
I’ve found that the best way to avoid tutorial hell is to constantly be learning new things, new ways to implement what you have learned. It’s much easier to learn something when it’s a part of a project as opposed to just reading about it or watching it on some videos.
I actively seek out projects that will stretch my skills and push me outside of my comfort zone, even if they are time consuming or difficult. However, the projects for this challenge need not be big, but they have to fulfill my criteria. They should be a challenge, but not too difficult. They must have some educational value. For example, with my first project on day 1- although a very simple challenge for myself in regards to where I currently am in my developer journey- I deepened my knowledge of linear-gradients. I’ve used it in the past, but I never really dove into the topic- just picked it up as a smaller piece of a puzzle.
Why on Earth?!
It’s never too late to start learning new skills or improving old ones. The best way to do this In the tech industry, is to set goals and challenges for yourself, and ultimately stick with them. Win the small battles by completing minimal achievable goals. I know it will be tough, and perhaps I’m biting off way more than I can chew. But I do know one thing. This can only strengthen my skills and make me better off in the long run. If anybody would like to join along, or simply provide feedback or luck, write me on twitter @jfusecodes.
Did you find this article valuable?
Support Joshua Mendoza by becoming a sponsor. Any amount is appreciated!