Learning is like riding a bicycle. It may be helpful to memorize the names of the parts, but you never learn to ride until you get on and try it.
I learn by doing. That’s how I experience our computer world. Merely reading or hearing about a computer topic doesn’t always translate directly into knowledge. So that is my approach to learning. Learn a few of the basics (like where the brakes are). Then try it out. Then go learn some more. (That’s why most of our CS classes have a lab component.) You may have a skill, like braking, but do you know WHEN to use it?
When you get far enough, you will have a need to know more, like how to fix a flat tire. It is nice to be shown how to fix a flat tire. But you are really ready to pay attention when you are staring at your own flat tire on your own bike and have a real need to know how to fix a flat tire NOW. (That’s why most of my classes have a project that let you ride far enough to get into trouble.)
I consider myself to be a guide. (I’ve guided my family to South Africa, Belize, Costa Rica and NASA.) A good guide will help you avoid the really devastating 300-foot falls. But you still have to walk the trail yourself. If you are interested in the computer path, come join us.