I find that with each project I get better at organizing and structuring them.
Therefore, if you can, try finishing multiple short games. The more games you finish, the more experience you have. And the better you'll get.
One problem I had with Angvik 2, because it took many years to make, I was stuck with old ways of coding that I'd felt like I'd out grown.
But afterwards, I made a short game over a few months, Nestris Legacy, and that was really refreshing. I learnt a lot from working on it, despite it being a short project. And now I feel better equiped for the next big project I'm working on.
I think you also get better at realizing how to make code that's more efficient. Using functions (and custom actions) more. Closing and opening groups more often, especially when that code doesn't need to be checked. I think optimization does help, with Angvik 2 it seemed fine for years, but then eventually performance gradually started getting worse and it was too late.
I have two objects for "global stuff" - a sprite (invisible, global) and JSON. The sprite is for variables I use often, and JSON for everything else.
The sprite also has Tween, Timer, and LineOfSight behaviors, so I can run occasional timers/tweens or cast a ray when needed.
yeah this is the best.
Also if you make it a single letter name. Then it can make it easier/faster to reference when you're typing expressions, especially when you end up using it so often.
Also, the commmunity Discord, has a #tips channel which is filled with hundreds of amazing ideas.