This book has a very concise writing style. I really wanted to keep it small enough to carry on an airplane (when we are allowed to fly again). I'm really proud of the final product and very happy with the editing staff at No Starch who helped me produce a very polished product.

Working through a technical book of any substance, as opposed to just reading or skimming it, will take dozens of hours, no matter how terse or verbose the style is.

The book is supposed to be around 270 pages, so verbosity probably won't be an issue.

I am right now working through "Python Crash Course" as an intermediate Python programmer. I very quickly read through chapters 1-8 so far and did all the exercises (rather simple ones), just to make sure that I'm not missing out anything on the basics. In the last couple of chapters, I actually picked up two or three pieces of knowledge I wasn't aware of. I spent around five to ten hours on this so far. This approach sounds terribly inefficient.

However, working through a beginner's book as an intermediate Python programmer, and only getting half a dozen of really new information out of it, gives me the confidence I need at this stage. So I don't consider it as a waste, but rather as an exercise in patience and repetition.

Why am I telling you all this? Because I think people overrate the monetary costs of books.

This is an interesting issue. I remember when I started studying discrete math, I actually bought two books. One was by Ross, and it's the one I prefer, but at places it was a bit terse. So when I had trouble understanding something right away, I looked at the same subject in Susanna Epp's book and usually I could find a relevant explanation or example straight away, but in the long term I couldn't stand this verbose style. (By the way, both books cost $80, but you can buy used copies at 1/10.)

I have the same frustration, though in this case I think given the author's expertise I imagine all the words actually contain much wisdom. Hopefully!