Introduction:
The best way to developing your scripting knowledge further, is to put your scripting knowledge into action, by practising making games out of it. Along the way, you may indeed encounter some issues with your coding workflow or issues that you have to try to solve and work around to get something to work the way you want it to work, but that is all part of the process of developing and learning from your own coding knowledge further, which can also improve your workflow’s flexibility.
By overcoming challenges along the way, you will learn more about the general process of scripting, including any of your own general scripting knowledge of writing code; even if this does not mean that you code completely unaided. You will then use both of your existing scripting knowledge, including any new knowledge of scripting you have learnt on the way, to be put into practise further and to help by learning and improving on it further.
Learning curves:
Think of it as this: every new game and every new script that you create within your game, comes with a new learning curve, especially if you try to challenge yourself hard enough. Of course, if you feel like you don’t have many learning curves then challenge yourself harder and more frequently by creating an even more complex game or a complex feature within your game, positively transforming your game and therefore positively transforms your coding knowledge further, than from before. Moreover, it’s also acceptable to have lots of little new learning curves too, and as any types of learning curve, are better than no learning curves at all!
Determination:
Additionally, and this is also a very important one: you need the DETERMINATION, to succeed in learning in the first place. There’s no point in developing your scripting knowledge and knowledge of coding, if you don’t have any passion or determination for developing scripts and/or creating games in the first place. Additionally, you also need the courage and determination to overcome any obstacles that may become apparent, in your way when your either testing your game out for the first time, or from testing out your game so many times and trying to find out what and why something isn’t working the way it should be. However, if you ever find yourself in the situation where your trying to get something to work but can’t get it to, then you can always look for, or find online resources. Even after you’ve tried your hardest to fix or solve a problem that still isn’t working, you can always step back knowing that you’ve put the effort and determination in on your behalf to get something to work, and that it is sometimes all you can do at that point in time and that is okay to feel that way but don’t give up the determination to try something else, try something new or to try finding a workaround and continue to learn by learn in smaller steps instead, rather than always having larger or bigger chuncks to overcome that you just don’t have the knowledge to and that you can’t at that moment in time.
Of course, if you want to learn quicker in bigger chunks then it can always sometimes be better to learn from it by somebody else. On the flip side though, learning by yourself can also be good too, of which that I have explained in more detail and thoroughly, down below.
It can also be good to try and learn solo and to try and solve smaller problems by yourself, rather than directly looking at answers for help, unless your stuck of course; (especially if you are more familiar and experienced):
Lastly, to some extent I believe that learning by yourself can also sometimes be better, than from learning by somebody else, as you are the one that knows where you are within your coding journey and your the one who knows the most about how much you already know about coding, even before you can start learning to code at a greater depth or level. You may learn quicker from yourself, by yourself, rather than from somebody else so don’t be surprised if that is the case.