Set yourself a goal (a game you want to | Official Unity Discord | Page 1

@vestal anchor There's a process that I've found to be pretty helpful in my learning journeys, and it's a bit more nuanced than this. I find that, in a given session, I might need to learn the theory, or I might need to learn how to apply the theories I know, and it's really hard to do both at the same time.
For example, when you write your first "Hello World", you usually don't know what static, public, void, etc. mean, but you have to just copy and past them into your code editor to get your code running. I consider this an "application" in the sense that there's a bunch of technical stuff going on, and you might not fully understand it, but you're using it towards some end.
When you find that you're copying and pasting a bunch of things that you don't really understand, it's a good time to dig into exactly what it is you're copying and pasting. For example, maybe you want to know what "void" means, and so you google around and go down a rabbit hole to understand function return types and such. It's not immediately useful or practical because you're just learning "theory", but it's really helpful to try to digest the things while it's contextualized by things you're working on.
In my experience, I hit a point where I've soaked up a bunch of new theory that I partially understand, and then I come back to trying to build something with it (thereby "applying" it), and then I rinse and repeat.

So I think a lot of people start by copying and pasting stuff into their editors and feel like they're not learning anything, but given that you don't know what you don't know, I think this is necessarily where you have to start with your learning. As things start to get mindless and confusing, it's a good time to slow down and try to understand what it is that you're copying and pasting

#Set yourself a goal (a game you want to