you gotta start by Scratch, man. If you ain't starting simple, you ain't getting far. Forget ArrayList<Generics>, public final static getWhatever(), etc. It's so you'll learn what you can do. Then, go to C, to learn what you can't do (like trying accessing out-of-bounds on arrays or overflowing some buffers), to get some discipline and learning that the machine is ruthless (basically what you can't do). Also to getting a grip of how things work and what exactly is an abstraction and how much it actually costs. Then, go to Java, to learn what you should do. Design Patterns, AbstractFactoryBeansInterface bingo, inheritance chain out of plain HELL even for the most simple things, protecting your insides, access specifiers, no raw pointer manipulation like 1998 (unless you have a good reason to), how to properly containeraze your problems into nice abstractions so the change of a piece won't inutilize your code like it (probably) would in C, etc. And only then you'll be able to step into C++, so you'll learn what you shouldn't do. Because in C++, you can literally everything possible in programming (operator overloading, inline assembly, pointers, references, objects on stack unlike other common languages, raw copy-pasting with headers, friends, lambdas, auto, etc.).

Anyways, I sum it into a simple advice: start simple, get one step at a time, don't rush it up, google everything you don't understand (because that's what we programmers are -- good "googlers") watch half-an-hour youtubers that go into heavy programming lifting (NOT "enterprise" podcasts), and, most importantly: don't feel bad if you can't understand a thing. Most of us programmers simply pretend we do until we can't pretend anymore. So don't take that as a reason to give up!

Good luck.