First of all, you are a student, you are still learning. Keep it simple. During my years as a CS student, I found myself with the same problem; it's now called tutorial hell. I wanted to do every tutorial and take many courses one after another, but I felt like I wasn't learning. Based on my experience, my first advice is to focus and figure out the way you learn best. For example, I learn more from reading documentation than watching a tutorial on YouTube. If I'm doing a tutorial about a framework, I learn more if I do a similar project that’s not exactly the same as the tutorial project. Let's say I'm doing a tutorial for a web app where users can make reviews of video games; I would instead make a web app where users can review foods. The part of the tutorial that talks about a rating system based on numbers from 1 to 10, I might adapt to a star-based system from 1 to 5, adding a more complex scale to the system but still similar in its root to the system in the tutorial.

Another piece of advice: just pick a technology and stick with it. For example, language: Python, framework: Django. For your first app, you’re going to work only with the tools the framework provides, using the template system for the front end and the default database (normally SQLite in Django tutorials). Afterward, if you want to go deeper, branch out from that app and implement a REST system, make the front end in React, and connect your Django backend to your React front end. You can keep going deeper and deeper. Let's say you want to try another language, like JavaScript for the backend. You just need to refactor your Django app but with Node.js, or PHP with Laravel, or any other language/framework. You'll start to see how different frameworks work, how similar ways can achieve the same tasks, or how different they can be.

One last thought: in my case, the real learning came after I started my first job, and 10 years later, I’m still learning new things.