My first programmation book was the K&R book. I hated reading it and was pretty sure that was nothing I would ever understand (or use). 25 years later, I now un

My first programmation book was the K&R book. I hated reading it and was pretty sure that was nothing I would ever understand (or use). 25 years later, I now understand all the details of the book. And now I hate ... the C language itself (with passion!). Fortunately, nowadays, there is so much learning material that you have the opportunity to choose the one that suits you. For example, I know that I cannot apply a theory upon reality. I have to start with examples and build my own vision by abstracting from a lot of examples. So I choose my learning material accordingly. My current interest, at the moment, is monad. Believe me, there is a lot of abstract articles about that. But my entry point was a tutorial about implementing some stuff in Javascript, that happened to be functors, monads, etc. Believe it or not, but I used that knowledge the week after in one of my Java projects. And my colleagues considered it was "a nice trick" (which is true!). In one word, the learning process must be fluid. Don't try to force anything. If the book medium does not suit you, don't blame the book. Or yourself. Try to find another resource and keep learning.