Think Python

Reading a book in the 21st century, especially a computer science book, is somewhat different than in earlier times. Today I finished "Think Python", which I read as a pdf on several different devices. Throughout the text were links to resources on the book's website, including large files for some of the exercises & examples. That's not all though; there's also a Github repository containing all the book's LaTex files as well as the code examples and files from the book. Naturally, while reading I discovered and oversight and submitted a pull request, that is, a correct to the files the author had placed there.

While reading the book, there were several places where I got a little confused. Ergo, I asked the python community some questions:

How to avoid modulus floating point error?

When is full list slice used?

Unbound method error?

And they quickly got answered. That's one thing I really love about python: it really has one of the nicest communities of programmers out there.

Overall, Downey's book was exactly what I needed to get up to speed on the language. The examples are no more difficult than they have to be, and there is plenty of wit reference various Monty Python skits and movies which keeps the reader entertained. I can see now why it's such a clear favorite!