Reading, digesting, internalizing, and interconnecting information to your internal knowledge pool is a time consuming process, no matter how much business demands want everything yesterday and how competitive the world gets. The true factor for me is time and I've found no shortcuts around it.
For me, I re-read multiple times with gaps of time between which allows me time to internalize information and then pickup and incorporate concepts I missed before in subsequent passes.
Often in a given set of knowledge or information, there are interdependencies that are overlooked by authors/editors and information you gather chronologically (or in the sequence present) later actually helps (or is even needed) to understand concepts correctly that you covered before (or may be outside to body of information you're studying).
Some gaps are omissions, some are due to gaps in your own understanding of a concept (everyone has them), some just require a lot of thought to properly internalize.
There's this trend of rapidly digesting and spitting out information as knowledge as a facade of understanding and I think neglecting critical thinking along the process is a fool's errand, personally. This leads to blindly following trends and taking everything at face value to me.
I couldn't count on my hands and toes the number of times I've heard people say "singleton" in the past 6 months who don't understand what it actually means or how/when to use the pattern (they're not developers). They heard some developer say it and then try using knowledge transfer to confidently use it outside the context where it actually fit because they never truly understood the concept but want to appear they do (instead of, for example saying, "hey, I've heard of a 'singleton pattern,' would that work here?")
For me, I re-read multiple times with gaps of time between which allows me time to internalize information and then pickup and incorporate concepts I missed before in subsequent passes.
Often in a given set of knowledge or information, there are interdependencies that are overlooked by authors/editors and information you gather chronologically (or in the sequence present) later actually helps (or is even needed) to understand concepts correctly that you covered before (or may be outside to body of information you're studying).
Some gaps are omissions, some are due to gaps in your own understanding of a concept (everyone has them), some just require a lot of thought to properly internalize.
There's this trend of rapidly digesting and spitting out information as knowledge as a facade of understanding and I think neglecting critical thinking along the process is a fool's errand, personally. This leads to blindly following trends and taking everything at face value to me.
I couldn't count on my hands and toes the number of times I've heard people say "singleton" in the past 6 months who don't understand what it actually means or how/when to use the pattern (they're not developers). They heard some developer say it and then try using knowledge transfer to confidently use it outside the context where it actually fit because they never truly understood the concept but want to appear they do (instead of, for example saying, "hey, I've heard of a 'singleton pattern,' would that work here?")