I hate it when there are grammar errors in scholastic books. (I worked my way through this book this summer (2012) as part of an independent study through a local college. If there are grammar errors, then I don't trust anything else the author has written because it could flat out be wrong. So, if something didn't work I had a hard time figuring out if I did something incorrectly or the author flubbed it--spent too much time on that one issue.)
Frustration 2: Implied: "We can teach you to do this, even if you don't know Python or how to write code." Umm, right. I had a clue, as I know VB 2010 and Java, and ran into roadblocks; for someone with no clue, not good.
Frustration 3: Someplace in the book there was a statement something like, "You should have a good map template if you want to create script to manipulate it." Okay, and how/where do we learn to do that?
Frustration 4: There were no hints of what to do if something didn't work. Basically, "here is my template, fill it in (from the examples), and there you go." (Life, ArcGIS, and Python are never that simple).
Frustration 5: No index. (Else I would give you the precise quote and page number re templates.)
Did like that the code was give for the try: and except: blocks, because that is a higher concept of coding and can be crazy to write.
Did like the discussion re progression and flow of code in the early chapters and creating the code outline/skeleton.