> I really want to go in depth into x y z Don't worry. Manuals are not supposed to be read like a textbook/tutorial. Not most of them anyway. I know a guy who

> I really want to go in depth into x y z Don't worry. Manuals are not supposed to be read like a textbook/tutorial. Not most of them anyway. I know a guy who read through half a thick book on Python without writing a line of code. He said it all made sense until a point, where he began to hate the language. Well, it was a terrible book for a beginner, but the point is, reading about the stuff is not enough and you will only get repelled. Choose one tech that you like. Investigate how real use works, mostly by trying to build real things, even if only for study purposes. If you get lost or the learning material gets repulsive/boring, move on. You need to have a good time. Seek existing useful examples by other people in real famous software not textbooks. Emulate them / reuse parts for your projects / invent, imagine new uses. You get deep by enjoying and "pushing the envelope" on what you can build. Not by reading per se. That is a parallel activity that can help, but is not enough. Many books/manuals are good for getting straight idea on which version of the tech supports the feature you need, and what is the version-specific syntax and limitations. But this is the kind of information that gets useful only after you already have a very good working knowledge of the thing and need to deal with real world ugliness of different versions/obscure features/corner cases at work.