Fruitdude i don’t think giving up your dream is a good answer. That’s an inner critic talking. We all have them.
The problem may be the tutorials themselves. The issue with these is while they show you how to make “a game,” you’re just doing copy work essentially. Copying a book of nuclear fusion by hand does not make you a nuclear physicist.
Game developing is DEVELOPING. It’s not one idea or concept but many shoved together in some form. You go in thinking you’re gonna make Pokemon when you don’t realize that game took a huge building full of people to make (yes even Generation 1) and it almost bricked their computers when they ran it. Games are made by teams - you may not be a programmer but dev teams are MANY disciplines. Find what piece you excel at. You’d be amazed how many people make a living just making menus. (somebody does it!)
Neil Gaiman says writers write. Developers develop. Make games not for others, but yourself until you get confident. Make games even if they’re crap because we don’t get good by being great at something off the bat - we learn by being terrible at it and learning from what we did wrong. Break things. Make mistakes. And take notes. You learn just as much from a disaster as you do from a success.
I, like you, was not a programmer. Programming books are a great help though (though strangely there is a dearth of Godot specific material in solid form at least, especially for v4) and this forum has been spectacular as well. Also - it’s ok to need a mentor. I recommend the videos of Masahiro Sakurai as well as the book Game Programming Patterns, which is free and well written from a developer’s standpoint.
All in all, you are only guaranteed to fail if you quit.