I have a goal in mind with every blog / video / book I read. Its a short decision matrix on whether I decide to skim something or not. E.g.<p>- Do I care about this article, is it useful to me next week? -> Skim read it<p>- Do I follow this author? -> Skim read it<p>- Is it news? -> Skim read it<p>I find that it is better off not deep diving into everything I read, and take most things with a grain of salt unless proven otherwise. This all of course depends on what you are reading, if it is all useful factual information, more consideration will be made.<p>If a topic interests me a lot, or an author I really trust, I will spend significantly more time reading slower. I only read nonfiction books recommended by people I follow, so I'll naturally read these slower.<p>For retaining information - I just use triangulation and swim in a sea of related topics. It becomes easier to tie information together later, when you've seen keywords and concepts already.<p>Anki is useful but I never have the time to write any flashcards down.<p>I think the best way to improve skills is to go through many rapid cycles of learning. Skim read, get your hands dirty with code if possible, reflect & write things in hackernews etc/talk to someone about it, repeat process as soon as possible. The faster you do this the more you can retain, read, and pickup new concepts.<p>After many rapid cycles take one slower cycle and spend more time reflecting on things learned