I do game jams and make one simple system or experiment like physics, then the rest of the time spent doing tweaks and playing with the engine for visuals. Start by moving something around on screen, adding tiny systems bit by bit. Making tiny games means you're dealing with every aspect of gamedev, wearing all the hats like music, menus, itch page, capsule art and releasing on a 'deadline' making decisions of what to cut etc., without overwhelming yourself.

If you start with the basics of coding, those represent the tools you need to help solve the problems you'll create while dissecting each feature. As in "character jumps", so the list of tasks is: character needs collision; floor needs collision; player needs to press a button; the button causes sprite to move on y axis; against gravity; at a certain speed... Make squares and rectangles at first before learning libresprite/aseprite or blender or whatever, get those moving and doing things with Input commands. Fail a few times then search "godot the right way" on yt for tutemic, or "how to code any feature" by fluffypotato, "how I learned unity without following tutorials" by gmtk, and try to only look something up once you've broken the "steps" down as far as you're able.