01
Name the job
A project collection may offer many starting points; a foundations text may promise a more connected explanation. Those are catalogue signals, not guarantees of teaching quality. Compare the descriptions and, where the retailer provides one, inspect a sample before deciding.
02
Look for a missing bridge
If you can reproduce examples but cannot explain their behaviour, look for the underlying model. If you understand the model but never build anything, choose a bounded application. You can move between the two instead of expecting one book to serve every purpose.
03
Compare the working environment
Check the language, API, edition, and any stated prerequisites. A relevant topic is not enough if the examples depend on a setup you cannot run. Record what you can confirm and what you still need to check.
04
Make the first session concrete
Before committing to the whole book, decide what you would do in your first reading session. A specific starting action is more useful than an ambitious promise to finish quickly.