Two parts of my learning strategy are thorough learning and reflection. Thorough learning meaning, for important things I try to understand the system end to en

Two parts of my learning strategy are thorough learning and reflection. Thorough learning meaning, for important things I try to understand the system end to end by reading unabridged and quality documentation, taking the time to comprehend along the way, realizing that this is a slow process but in the long run worthwhile. Reflection meaning that after a learning period I'll take time to reflect, on the meta level, how things are going and what I could do to improve. I reflect by keeping a log, with an entry for "thoughts" and an entry for "lessons". In the thoughts section I just freeform write whatever I felt about the recent learning period and in the lessons section I summarize any actionable things from my thoughts, if any (and I don't force myself to come up with lessons if there aren't any). Generally, if I struggled a lot with something I'll pull lessons out and if it was easy I may not have anything in the lessons section. For example, last year I started using python more at work. I've known python in the sense that I could write scripts in it and generally understand it, but my knowledge was mainly based on having seen python scripts, intuition, and Google searches - and mostly python2. Putting my first principle into play, I looked at the python documentation and read it end to end. I tried to read one section a day, though some sections are more or less dense so that was very flexible. As I read I had a Jupyter Notebook open and played around with every concept the documentation described. When I was done reading I would spend a few minutes writing my notes as described above. This took maybe 30 minutes a day, most days, for a little less than a month. On top of this I would randomly do leetcode problems in python and write python scripts at work, but at the end I felt I understood what I was writing and why in python much better.