I'm just now finishing up a semester teaching a CS0 class from this text. In a nutshell, I am teaching the same course next term, and I will not use this book again. Let me add a few useful things for the reader before I explain why.
First, there are essentially two classes of texts out there for CS0 classes: (1) surveys of computer science qua science and (2) surveys of the information technology field. Snyder's book most definitely falls in the second category, although there are several chapters devoted to JavaScript.
Second, if you're going to use this text, make sure you get the online resources, especially the prepared labs and the 6-page PDF reference for JavaScript. The labs are detailed, deep and very useful, and the reference is well-organized and easy to use.
In fact, I did not have a chance to review this text before I adopted it for my course, and it was the labs (along with a solid-looking table of contents, credentials from the National Research Council, and a single 5-star review here) that convinced me to use it. I do hope this review will discourage others from doing the same.
My problem with this text is, in a word, depth. Or rather the breathtaking lack thereof. It is organized coherently enough, but time and time again throughout this term, I found the treatment of various topics in the book so shallow that I had to spend almost double time filling in enough details to make things coherent to my students.
The result was an absolutely enormous amount of work on my part, finding supplementary readings, putting extra care into lectures, writing extensive tutorial materials for the assignments, and so on. At every step of the way, I felt that I was fighting the text, rather than drawing from it.
Some of the worst habits in the book's writing include:
*_Long_, drawn-out analogies for ideas that are never given any other explanation, so that the "analogies" are completely devoid of context, and hence pointless. Invariably, such things serve only to muddy already-murky waters.
*Gross over-simplification of many concepts, so much so that it is nearly impossible for a student to develop any sense of the real-world ideas that made a technology worth adapting. Perhaps the most egregious example of this is in the chapter on encryption, which in its presentation of RSA pretends that only one public key (3, 55) is ever generated, and but then proceeds to give a "formula" for computing the private key, before devolving into the spectacular silliness of a quotation of Euler's Theorem that by this point might as well be in the original german for all the good it would do a student.
*Absolutely _awful_ problem sets. The few "exercises" that aren't just fill-in-the-blank and multiple-choice review consist of short-answer problems that alternated between the trivial and the pointless, or combinations of the two. The "test banks" are no better. With almost no exceptions, they were questions I would consider insulting to a six-grader, let alone a classroom of college students.
The really strange thing about this is that the website for Snyder's own version of the course looks quite well organized and rigorous. In fact, the look of his class from that site was one of the reasons I selected this text. Some of this is the use of those lab assignments I mentioned above, which are quite nice. And Snyder's work with the NRC clearly indicates a fair amount of thought went into the design of this work.
The only explanation I can offer for the disconnect is that he has simply been unsuccessful in putting into writing some of the apparent magic of the course from which this text arose.
But the book does not pull it off, all my self-consciousness about armchair-quarterbacking aside. Good work with NRC report, but the book from that effort is still to be written.
