[troelsSteegin]

Read less, and read with a problem in mind.

If I were reading about about Rust, which I am not familiar with, I'd be focused on what's different about Rust relative to languages I am familiar with and what problems the authors say it solves. How might I solve X with Rust? I'll read the introduction deliberately, toward what is the intention of the authors for readers of this book, and look at both the table of contents and index in terms of seeing what's there. Then I'll skim, and dive in where it's relevant at the time.

Tacitly, I am viewing a non-fiction book here as a searchable index of concepts and examples vs as a purely linear narrative.