I found the best way I learn from books is if I have already been immersed in a project for a long time and have accrued a long list of unknowns, then the books

I found the best way I learn from books is if I have already been immersed in a project for a long time and have accrued a long list of unknowns, then the books and videos become more interesting as I gather information on tackling those long standing issues. For my style of learning, trying to become an expert (and memorizing everything up front) is a doomed strategy. For example, I've been working on an electron, c++/wasm and typescript app for around 2 years. I interface with a large c++ program and I knew diddly about c++ for most of those 2 years, just doing the least damage I could do if I did need to modify the code. Lately though I've been soaking up more technical content about it and really enjoying it, as more and more of those questions I've had for a long time are getting answered, and I'm starting to feel more competent and satisfied when working with c++. Maybe this example can give you some ideas on how to get more engaged with the content by already having pressing needs.