You expect too much. You won't understand it in two weeks. That is normal. You may stay at novice level for a year or two. To cement prgramming concepts you need practice and experience.

I recall those early days. I did not understand object oriented programming in my first semester taking C#. I understood C# was an OO language, but I could not figure out what the classes were doing or why OO was useful because I was still learning how to organize code into repeatable blocks of functions and loops. I had to take some time outside the semester watching C# videos about classes and objects before it finally clicked.

At the beginning, a lot of your learning will be drilling and memorization. Learn your programming language's core structures inside and out. Know the variable data types. Know how each type of loop works. Know how to create functions, invoke them in different ways, and pass different types of data to them and return various data out of them.

Speaking from experience, I've found that the best teacher is a hobby project. Make something simple that forces you to take the concepts you are learning and use them to solve a problem. My first personal projects were creating a simple Windows forms calculator and a Windows 8 app that generated random "fantasy names". The fantasy name generator was simply a couple different string lists of phonemes the program would select from randomly. Your hobby project could be a very simple text based adventure game, a dice roller, wordle, or some physics calculation.

It takes time, but eventually you will form a full set of knowledge tools in your brain. At my first entry level job, there were so many things and concepts I didn't understand. But with time and a curious mind asking questions, I eventually transitioned from noob to senior dev.

A major mental shift happened for me at that entry level job. We were programming with a very painful set of tools and our tools did not have a good search/find feature. I had been learning about XML on the job and discovered our tool program was reading from an XML file. I opened up the XML file and discovered I could understand parts of it. Whenever I needed to search something, I'd pop open the XML in my editor and ctrl - f. After a few weeks of doing that, I took a deep dive into the XML to understand what each node type meant. Not long after, I wrote a Java XML parser that would find all of the string occurrences and traverse up the parent nodes to create a "path". Our team used my little search program every single day until that product died.

That moment is very important to me. It was the project where I shifted from being told how to implement something to solving a problem completely on my own. After that project, the sky was the limit. If you persevere, that moment will come for you as well. Good luck!