This was actually the second time I stopped learning game development and it was for the exact same reason and at the exact same lesson; basically I was learning 2D game development, got to the stage where you set up the sprites and can decide how long each sprite lasts for (so perhaps one frame in a several frame long sequence you want that one sprite to last on the screen a little longer than the rest, you can), and also setting up each sprite and such, only to realize I'd have to do this for everything that has sprites and was like noooooooope.
Maybe if I ever try to learn game development again I'll just stick to ASCII games or something. I watch the game dev videos where people make games in a short amount of time, see all the work that goes into the stuff they do, and realize it's not for me.
I'm honestly way too lazy to do any of this stuff. I wanted to be a game developer ever since I was a kid, but I'm also infinitely lazier now than I was back then.
This is why game development tends to be a multi-person endeavor, and why it's super important to measure your expectations and be flexible. Like I've got game ideas of my own, but I 100% accept that if my ultimate dream video game would actually be made, that most of the ideas would have to be scrapped, and I'd need to find several people to help me do everything.
Ultimately, though, even if you just draw concept art and write a huge document detailing every idea you have and how these fit with each other (as if 90% of it wouldn't be cut for one reason or another), and make a short barebones tech demo or however we call it, you're still expressing your creativity and building skills. So it isn't really a failure, it's still a step towards achieving your dreams.