Comment by Otterly99

Well said. I use it the same way. Sometimes, a technical book will assume that you know a concept or will even use an acronym that is not explained (but obvious) or is just plainly not very explicit. I also use it to directly test my knowledge of the subject (you have to be careful of the people-pleasing behavior, but in my experience they tend to gently tell you where you're wrong rather than lie to you). Same goes for hands-on books. Sometimes the example are not very interesting, or you have something of your own that you would like to try. As long as you use it carefully like this, it can be really transformative. I do agree that there is a potential risk of offloading too much thinking to it, but if you keep that in mind, I don't see the problem.