Bonnie on college student reading skills

from the Headsprouts thread:

Reading comprehension is a huge problem for my college students. The introductory CS textbooks are written using vocabulary and a sentence complexity that is way beyond them. I wish I had a better sense of their actual reading skills so I could do some vocabulary work with them. The gasstationwithoupumps blog has posted links to some excellent material on teaching students how to read technical material that I think I may use next semester.

Bonnie on peer review and textbooks in computer science

Bonnie writes:

Peer review in computer science is very weird, because unlike other fields, we mainly publish in conferences rather than journals. It is a huge issue at tenure time because tenure committees assume that conference publications are meaningless - and they are in most fields - but not in computer science. Most of our conferences have acceptance rates of around 25%, and the top conferences are below 10%. That is where the peer review is happening in our field.

But that is research peer review, and I thought we were talking about textbooks. In CS, there are textbooks for certain "standard" courses - intro to programming, databases, operating systems, theory of computation, and a few others. The only real churn that I see is in the intro to programming area, because every time a new programming language hits the scene, you get 10 new books doing CS 1 and 2 in that langauge. In databases and operating systems, the same 3 or 4 authors have dominated for 20 years, issuing edition after edition of their book. So in reality, professors adopt the textbook, which isn't purchased or read by most of the class anyway, and then add lots of their own material. For courses that have no reasonable textbook - for example, everyone is adding courses on Android programming right now - we simply have the students buy a book aimed at professional developers, or cobble together notes on our own.

And here is Allison on peer review in mathematics.