My 'self-taught developer experience' as a teenager is too far back to be any useful today I guess, but when I learn a new technology (like a new programming la

My 'self-taught developer experience' as a teenager is too far back to be any useful today I guess, but when I learn a new technology (like a new programming language) I usually don't use any '3rd-party-material', but instead just lock myself into a room with my computer and just use whatever there is on 'original' documentation. The next important thing for me is to set myself a practical goal that seems achievable in a relatively short amount of time (preferably something I had already done before in a different context). For instance for a new programming language that could be "I'm going to write a Tetris or Pacman clone", so that you are forced to tackle actual real-world problems instead of just following the documentation examples. Just passively reading a book or watching a video tutorial never works for me. I need to tinker and experiment with my own hands and refer to the documentation for guidance only when I'm stuck.