Read code. In paper. Do not clone a repo, compile it, and run it. Get code about something you want to learn about, or code written by someone you admire, mak

Read code. In paper. Do not clone a repo, compile it, and run it. Get code about something you want to learn about, or code written by someone you admire, make a printed copy, and read it carefully. Follow how stuff is done. Try to understand the hows and whys without a compiler at hand. Without documentation. Then, start looking for stuff you don't know how it works and consult documentation only after you cannot figure out what's happening. I learnt a lot of C++ and Win32 this way from Microsoft Systems Journal (a long time ago). And believe me, it works.