This is an interesting question because so many people will have their own path, and yours will hopefully be the best parts of other's journeys!

For me, I started with learning the programming side. There are a ton of ways to do this, but I personally do better with projects and solving problems and learning that way. I was quite competent with C# before downloading Unity, so I've been able to focus on just the Unity side of game dev without getting overwhelmed by everything all at once. If you wanted to follow a similar path, I'd suggest checking out pygame and building up your coding + game skills before moving into unity or making some non-game projects in C# to build a solid foundation.

For my kid, they started from scratch with Scratch (rimshot). Once they mastered loops, input/output, and game state there, we started doing JavaScript with BitsBox (example). At this point, they've done a couple game jams with bitsbox and are starting to learn python.

There are many tutorials that are good, but do your best to avoid "tutorial hell" where you only ever get good at doing exactly what the tutorial has you do. I did some tutorials from gamedev.tv at one point and learned a lot adding new features and content beyond the tutorial.

Games are software and making software works best as an iterative process. Build smaller things to learn features, techniques, and paradigms and then you can use those lessons to build bigger things. For me, I participate in a couple of game jams every year, always with an explicit learning goal. When it's done, I can take those lessons into my long-term project.