Answer:
Balancing between theory and practice
You need to get some sort of baseline understanding of what programming is and how the basic structures work before you can build anything. This requires reading, some memorization, and seeing a lot of example code.
Reading and working through sample problems is good and necessary. There are hundreds of free PDFs and tutorials (interactive or not) that you could work through. You could spend years going through those.
At some point, though, just reading doesn't work. It's dry and can be quite boring. You'll find your mind wandering or wanting to distract yourself. You won't understand how the code is actually used in practice. Or how you will use XYZ concept in the code you want to write or the thing you want to build. If you don't actually use the knowledge you're reading, you won't really know it and encode it into your brain. Encoding is a crucial part of learning.
You probably need to learn to code because you want to build something. Programming is a means to the end of building something awesome.
So you might have awesome motivation and discipline to build your awesome app but you first need to have enough knowledge to be able to do so. You'll go try to set it up and find you don't understand enough about functions or variable scope or for loops (or one of the many many other concepts).
So it's a bit of a catch-22.
Read too much theory, get bored, distracted, and you'll forget most of what you're learning.
Try building something without enough theory, get lost and stuck.
So the balance to be struck is to be constantly learning just enough theory whilst tinkering with and putting into practice (code) the theory that you are learning. This way you're having fun and learning at the same time.
Explanation:
