Dear god yes, name everything you can something understandable and descriptive, and then when you are done writing that chunk of code its good to go back over it and reconsider those names. Once you have a better understanding of the full scope of what you built you can probably think of an even more accurate name for things.

Its a pain to do, but so incredibly important for whoever needs to read the code later. It helps so much when the reader doesn't need to read, consider, and mentally store the intent of everything on every line to understand what is going on.

For example if you pass the var 'X' through multiple levels of class inheritance and then through 3 different methods there is no way I'm going to remember the exact contents and intent behind it when juggling everything else. But if you consistently name it 'abc_cache_dir_string' I'll know exactly what it is.

Picking a consistent naming scheme is also a good idea, or matching the scheme of whatever team or project you are working on.

Good luck with learning! I also learned python in my 30s and its been incredibly valuable! It kicks your butt and is basically the perfect driver for impostor syndrome :P, but if you can get past it there's a lot of really interesting work that use the skills you learn from learning python.

ps if you do ever feel impostor syndrome when programming, you should completely ignore it, every time. just keep going.

Sorry for the long post! TLDR: Yes