I too started with a bit of understanding already in place, having worked through "Basic" history. C64 basic to AMOS (Amiga) to Visual Basic on PC.
(plus a dozen other scripting "languages")
So I got the flow of Construct2 quicker than when I made the move to VB with it's event driven code. (Sort of like triggers in Construct2.)
I don't want to suggest newcomers all start making Flow Charts, (I've never found them useful.) But the first lesson should be grasping the concept of organizing the game to do and handle everything needed without ending up with unmanageable spaghetti code too complicated to finish.
There are good tutorials, Kittiewan's match game tutorial was the first I used. A bit advanced, but it was closest to the puzzle game I had in mind. (Pucked)
Another good one is Kyatric's "Asteroid clone in less than 100 events" he covers the planning and thought processes very well.
So for a list of progression, I'd say do the Beginner's guide, then start looking for tutorials that are similar to what you want to make.
Trying to get through a tutorial you don't have any interest in, will make it more like "work," and it should always be fun.