Tutorials, books, courses, and technical documentations are important, but there is another important thing that is practice.
Reason #1: Make a space for practice
Building a new project will give you a space to practice.
Practices can be tedious at times, but according to James Clear's book Atomic Habits, you can eliminate boredom by doing something small to make it more enjoyable, easier, and more likely to make you love it and push you to do it consistently. No matter how minor the changes you made to your project were, they were a first step toward sharpening your skills. If you're stuck on what changes do you need to make? Here are my tips. If you already built a project you got from the tutorials or you built it on your own, then go ahead and practice by adding some small features to it, like a button that can change the background color based on day or night, adding some sorting data, adding a filter, and many more.
Warning: Don't practice too much or you will hate it.
Reason #2: The places to discover new experiences
You will have new problems when you build a project. Use that as your opportunity to level up your problem-solving skills.
Those problems you solved are important for the future of your projects. For example, when you face the same problem again, it will become easier. It gets easier or you get more advanced solving methods when you face it continuously.
Stuck on a problem? Stop forcing yourself to solve it. Take a breath and read some meme.
If you are stuck on a problem you face, don’t force yourself to solve it. I have experienced this before. Forcing ourselves to solve problems that are difficult for us is a bad thing. You are becoming less mindful and, in some cases, your solution becomes a new problem. Try refreshing your mind for a while by walking around, taking a wash, stretching, or quick exercise. When you feel refreshed, take a look at your problems on stack overflow. Read it in detail to get a deep understanding of the solution. Don’t just copy and paste. Remember, this is your personal project, no need to rush. Your main goal is to learn not to finish it.
There is no need to force yourself to solve a problem quickly. Sometimes we need to refresh our minds. The goal is to learn not to finish it quickly.
Reason #3: The sandbox tools to try any tech stack
Sharpen your skills in choosing the right tech stack.
Exploring any tech stack is the way you to level up your skills and get wider knowledge of the tech stack.
Reason #4: Becoming your creativity booster
Don't limit yourself to being creative. Doing whatever you want is a part of practicing your creativity skills.
Reason #5: Becoming the history of your learning journey
The common problems of projects that are not updated or not maintained Even though there are so many experiences we can get from them. If you join a new organization, these skills are usually needed. Commonly, you face this problem with an old and unmaintained project. Whatever your projects are, there are already solved problems out there, or the tech stacks are too old. Maintaining it will teach you new skills such as refactoring, updating dependencies, changing deprecated dependencies, and more. There are many problems that need to be solved, and worthwhile experience will come from maintaining projects.
However you feel your old projects are bad, it is still proof that your skills are improving. Don't delete it. Give it a small maintenance to make it equal to your skills now.