In the 8 bit days there were programming books meant to be read back to back. I loved them as a kid - though I'm not sure that I learned much from that exercse. Even K&R "the C programming language" (first edition, the second edition wasn't as readable from what I remember, though that might be just because it was too repetitive for someone who had read the first edition) could be read that way.
These days that isn't a good use of paper books. There is rarely any reason to start with any one construct, and if you are not a novice programmer you know there must be something that does what you need and don't want the book to assume you understand the syntax of the while loop when you look up the do-while loop.
But I do miss out on in-depth knowledge of a library or language that way. But there is no value in gaining said in-depth knowledge when the stack & libraries I work with changes every couple of months or years.