Speaking as someone who has recently started re-learning development...
Don't quit. Take a break, do something else for a bit and come back to it. Sometimes a fresh perspective is all you need.
You can spend all day, weeks or even months trying to figure out "what to build". The truth is, it doesn't matter what you write. Just write some code. Then pick something else and write code for it. Alternatively, write the same thing a different way or in a different language. When you've iterated through a few things, take a look at your first thing. See if you can improve it using the the new things you've learned.
I have to remind myself of this. Sometimes I just don't get things, but that's ok. You don't have to understand exactly how Console.WriteLine() works to write Console.WriteLine("Hello World"); Learning the ins and outs takes time. The rest comes with writing more.
Programs are just big problems broken down to little problems which are then solved. Break the problem down into little problems. Then work backwards and try to solve those little problems until you come up with a solution. (See what I did there?) If you can't figure out how to solve a problem, consider breaking it down some more until you can solve it.
Sometimes it's your enemy too. Google-fu is helpful, as long as you know what you are looking for. If you don't, you may have to reword stuff until you do find something.
They do, but only to a point. They help you with the basics, but anyone can follow a set of directions. (Well, apparently my kids can't but that is another story.)
Part of learning to be a developer is being creative. Sometimes a tutorial can be word for word instructions, I like to think of them as a series of very loose guidelines that I probably won't follow anyway.
Just write something, keep writing something until you understand and then write something else. The rest comes with time.