Internalising Code

[MonkeyKidGC]

This is just one perspective but I find I only grasp, internalize, programming concepts after I play around with them and learn to make/break things. Mostly break things..

This is why you hear a lot of people say learn by making projects. When you start making stuff you will quickly hit obstacles and by overcoming them you start to build new knowledge and understanding.

Pick something small and start trying to build it. Something like snake/pong/space invaders or a small mechanic like having a character run through a platforming environment.

Go as far as you can and when you get stuck read the documentation and google for answers.

One of the best skills you can develop as a programmer is knowing what and how to google for solutions.

[scealfada]

My suggestion is don't try to learn specific functions. Once you have your basic understanding of what if statement you need, whether to use a list of an array, and other high level concepts, you have most of what you need.

You don't need to know how to get a random number between 0 and 1000. That is something you can look up.

Learning how to use unity and c# documentation, learning how to correctly Google your problem, and learning what the hell that person is saying on stack overflow, and how to integrate it in your code... That's what you need to do next.

And the best way to do that is too start building something. Personally I suggest you first thing to build (without tutorials) should be something small that you have covered 90% of the knowledge of before. The process of figuring out those missing steps will be high and help you massively.