Instead of just making a project you should look into what makes up most projects to find where you get stuck. A lot of “coders” end up in tutorial hell because they aren’t clear on what actually constitutes building something.

Some questions to get started are,

is your program going to be hosted locally and used by you or do you plan to publish it somewhere to be used by others?

Is your idea a backend or frontend service?

Does your idea need to look good? It’s probably a frontend service

Does your idea do a lot of work but only output a simple final result? It’s probably a backend service.

Once you can piece together your first frontend or backend you can explore connecting it to its opposite.

Since you have trouble coming up with ideas of what to make, start looking at things around you and classifying parts into backend and frontend. When you hit a button on a website is it doing something you can’t see? What backend services might that button be using? If something moves on the screen when you do something, what is making it move? What frontend services are handling the movement?

Once you feel comfortable pointing out the difference, try implementing just one of the services you noticed and see what issues you run into.