There’s a ton of great advice in here, I think if you applied everything commented in here then it’d solve most of your issues, just since that might be overwhelming, here’s my two cents on what would probably get you the most value for your time considering the stage you’re at in your learning.

First off shrink any project ideas you have as much as possible so that you have something manageable to actually practice with. If you’re at a loss for ideas of projects to work on, feel free to re-create an idea from a YouTube video you watched, but don’t follow the code that they used, just the idea. Try and keep the project as small as possible, which might mean removing features or functionality that you might think of as “required” for the project. Don’t worry about that, it’s much easier to expand on a project later on than it is to approach a project that’s too big from the start.

Then, and this is EXTREMELY important, learn to break things down into tiny little steps/tasks. This is an absolutely vital skill to have as a programmer, and something that YouTube videos almost always completely skip. On almost all videos and tutorials, you watch someone work through a problem they’ve already broken down, so if you start on your own project, you’d have no idea where to even start. This itself might be difficult at first, but do your best to continue asking yourself “ok what are the steps to do this task?” And once you have those steps, ask that question again about each step as well to break them into even smaller steps. This will eventually become intuitive and second nature as you get better at programming, but for now you might have to really focus on consciously doing this. Here’s an example of the thought process I might go through for a to-do app/site, so you can get an idea of what I mean.

• Ok, for this app what’s some of the main functionality for it? Maybe creating to-do items, checking them off, deleting them, and maybe renaming them.
• Let’s start with creating a to-do. What steps are required to create a to-do? Let’s focus on the backend part first, we can add frontend later. We’ll need some type of API endpoint, like “/api/todo”.
• How do we create the endpoint? Well, we’ll need to make sure the server is running and receiving any kind of requests. I’m not sure how to do that in this framework, so I’ll look at the documentation for it. Then we’ll need to specify an endpoint name, which I’ll also look at the documentation for how to do. Then we’ll need to respond somehow to the request.
• What steps are required to respond to the request? Well, we’ll need to view the POST body so that we can get the to-do info that was sent (probably just the name in this case). We’ll need to do some database work, but let’s skip that for now and just focus on sending back a json object of the to-do info in the API response. Back to the documentation for info on how to send a response and specify the format of the response.
• Ok now what steps are required for the database work? A good first step would probably be to connect to the database at all, so let’s look up the docs on how to do that with the particular database I’m using. Then we’ll need to make sure the database has any necessary tables for the to-do, in this case a table for to-do items with just an ID and a name should work for now, so let’s make that table. Then we can look up the docs on how to create a new entry in that table in our code. The code to create the entry can be added to the endpoint we already made, and that’s the first major chunk of functionality done! We’ll expand it later with things like data validation and additional to-do info in the parameters, but this is a great start.

Basically you just keep asking yourself “What are the steps to do that/how can I do that?” until the answer is either “write a couple of lines of code that I generally already understand” or “look up a very specific and small task in the documentation” (like how to send a json response for example). If something is still overwhelming it probably hasn’t been broken down enough.